VS debugging issues [modified]
-
I'm using the IAXClient[^] library in CodeProject. The problem is when I debug it, I sometimes get heap corruption errors or sometimes it doesn't registers with the server. It works completely fine in Release builds and in my colleagues PC (checked on three machines, worked fine there), but doesn't on mine. Way back earlier, it worked fine, but that time it didn't run properly outside VS (i.e. I had to run from inside VS otherwise would get heap corruption errors). This is the exception I get while debugging in VS
Windows has triggered a breakpoint in SharpIAX.exe.
This may be due to a corruption of the heap, which indicates a bug in SharpIAX.exe or any of the DLLs it has loaded.
This may also be due to the user pressing F12 while SharpIAX.exe has focus.
The output window may have more diagnostic information.
The call stack looks something like this
> ntdll.dll!7c90120e()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!7c96e139()
ntdll.dll!7c96e576()
ntdll.dll!7c96f75e()
ntdll.dll!7c94bc4c()
ntdll.dll!7c927573()
msvcrt.dll!77c2c2de()
iaxclient.dll!037b8d61()
iaxclient.dll!037b9029()The fact that it works fine on other machines means that the code may be fine and the problem is with my system or so. And now I want to debug the cause? Any clues? I'm using XP SP3, VS 2008 TE **EDIT:**Found this message on the Output window of VS
HEAP[SharpIAX.exe]: Invalid Address specified to RtlFreeHeap( 003C0000, 01389A5C )modified on Wednesday, June 16, 2010 2:27 AM
-
I'm using the IAXClient[^] library in CodeProject. The problem is when I debug it, I sometimes get heap corruption errors or sometimes it doesn't registers with the server. It works completely fine in Release builds and in my colleagues PC (checked on three machines, worked fine there), but doesn't on mine. Way back earlier, it worked fine, but that time it didn't run properly outside VS (i.e. I had to run from inside VS otherwise would get heap corruption errors). This is the exception I get while debugging in VS
Windows has triggered a breakpoint in SharpIAX.exe.
This may be due to a corruption of the heap, which indicates a bug in SharpIAX.exe or any of the DLLs it has loaded.
This may also be due to the user pressing F12 while SharpIAX.exe has focus.
The output window may have more diagnostic information.
The call stack looks something like this
> ntdll.dll!7c90120e()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!7c96e139()
ntdll.dll!7c96e576()
ntdll.dll!7c96f75e()
ntdll.dll!7c94bc4c()
ntdll.dll!7c927573()
msvcrt.dll!77c2c2de()
iaxclient.dll!037b8d61()
iaxclient.dll!037b9029()The fact that it works fine on other machines means that the code may be fine and the problem is with my system or so. And now I want to debug the cause? Any clues? I'm using XP SP3, VS 2008 TE **EDIT:**Found this message on the Output window of VS
HEAP[SharpIAX.exe]: Invalid Address specified to RtlFreeHeap( 003C0000, 01389A5C )modified on Wednesday, June 16, 2010 2:27 AM
You should ask this on the article forum instead. This is not the place to post this question, as it is more likely that somebody who uses the library will have encountered this issue than somebody here, and, more importantly - if it is solved, the fix should be visible against that article.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.