You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2016/01/07 14:07:39 UTC
[jira] [Closed] (PROTON-226) Porting Issue -- Heap Corruption using
Visual Studio when running client/server proton in debug mode.
[ https://issues.apache.org/jira/browse/PROTON-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell closed PROTON-226.
---------------------------------
Resolution: Fixed
Closing this as comment indicates it is likely fixed via duplicate PROTON-402, and there has been no activity on the JIRA since.
> Porting Issue -- Heap Corruption using Visual Studio when running client/server proton in debug mode.
> -----------------------------------------------------------------------------------------------------
>
> Key: PROTON-226
> URL: https://issues.apache.org/jira/browse/PROTON-226
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.4
> Environment: Windows using Visual Studio 2010
> Reporter: Mary hinton
> Labels: build
>
> Code changes for windows port were added (MinGW and Visual Studio) to the proton codebase recently.
> Using the new codebase and some additional changes, I ran the proton executable using the Visual Studio toolset as both a server and client. When the client exits, a Windows popup displays:
> "Windows has triggered a breakpoint in proton.exe.
> This may be due to a corruption of the heap, which indicates a bug in proton.exe or any of the DLLs it has loaded."
> Still tracking this problem down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)