User forums > Help

stop at ntdll!DbgUiConnectToDbg () on debug start

<< < (2/4) > >>

Rytz:
I had an issue with the boost filesystem library that raised the same error only when I was debugging it.  I was able to fix the issue by setting the program to run on one processor (I'm running a dual-core system).  You can do that permanently (at least in XP) by setting the program compatibility mode on the executable or you can set the affinity at run-time by using the task manager (I think I still got the error with this method though).

I saw this thread before when I was having my problem so I figured I'd share this little tidbit :).

nanyu:
I found the answer from http://n2.nabble.com/Invalid-Address-specified-to-RtlFreeHeap-and-libstdc%2B%2B-problem-td2092059.html

Code::Blocks does allow you to automatically send commands to gdb after it
starts though.  Select "Compiler and debugger ..." from the Settings
menu.  Click on "Debugger settings" in the left pane of the window that
pops up.  Enter the commands you want to send to gdb in the "Debugger
initialization commands" textfield in the right pane.  (And entering
"handle SIGTRAP noprint" worked for me.)

Fett:
I had the same problem. I solved it, when export my project in m$ vs, and vs's debugger show me where i did mistake- it was then i use "delete" statment. i hope in future mingw32, and gdb will have a more(maybe most) powerful dev tools   :).

ollydbg:

--- Quote from: Fett on June 28, 2010, 08:06:10 am ---I had the same problem. I solved it, when export my project in m$ vs, and vs's debugger show me where i did mistake- it was then i use "delete" statment. i hope in future mingw32, and gdb will have a more(maybe most) powerful dev tools   :).

--- End quote ---

Which gdb version did you use? I guess you have an old version of MinGW GDB, so please update it first. And if you post your test code, I'm like to test for you. :D ( I don't have this problem)

eigen:
Sorry to bring this old topic up, but I have a similar issue. When starting an app in debugger, or any app in debug mode, first I get TWO (always) error messages in a row:



and then the debugger tells me

#0 7C964ED1   ntdll!RtlReAllocateHeap() (C:\WINDOWS\system32\ntdll.dll:??)
#1 7C93F8FB   ntdll!RtlInsertElementGenericTableAvl() (C:\WINDOWS\system32\ntdll.dll:??)
#2 7C90EAC7   ntdll!LdrCreateOutOfProcessImage() (C:\WINDOWS\system32\ntdll.dll:??)

If I put gdb.exe in the app folder and drag the exe onto it, I get the RtlReAllocateHeap error. But when I do the same in my gf's computer, all works as expected. So, something must be totally messed up in mine.

The thing is, a simple console "Hello world" works fine in the debugger, but as soon as the app has to get ANYTHING from an external dll, it crashes in debug mode. Even an additional line of SDL_Init(SDL_INIT_VIDEO | SDL_INIT_AUDIO | SDL_INIT_TIMER); is enough to throw the RtlReAllocateHeap error when starting the debugger.

Everything is working in release mode, as well in the debug mode a few days ago. I don't think I have changed anything in the system lately .. So, have you guys got any ideas what it could be? As a last resort, I'm thinking of re-installing Windows, in case there's something messed up internally. Maybe the ntdll.dll is somehow broken, though the file size is exactly as it should be, so I don't think it's been modified.

Thanks in advance,
Eigen

Navigation

[0] Message Index

[#] Next page

[*] Previous page