From: Rafael F. <ra...@ne...> - 2008-04-18 19:49:16
|
Doug Schaefer escreveu: > Rafael Fernandes wrote: > >> Hi, >> >> Does anyone use Eclipse CDT? >> When I debug an application with it, gdb stops many times at >> ntdll!LdrAccessResource(). >> It still works fine after I send "continue" to it, but it's annoying to >> do that everytime I debug. >> >> The call stack is like this: >> >> 6 ntdll!LdrAccessResource() 0x7c90eb94 >> 5 ntdll!ZwMapViewOfSection() 0x7c90dc61 >> 4 snwprintf() 0x7c91c3da >> 3 ntdll!RtlValidateUnicodeString() 0x7c916071 >> 2 ntdll!LdrShutdownProcess() 0x7c9162da >> 1 <symbol is not available> 0x00000000 >> >> I'm using gdb version 6.8 >> >> Did anyone else have this problem? Any ideas? >> >> Thanks. >> >> >> > > Yes, this is something I've been trying to figure out too. I'm convinced > at the moment that it's because of the way the CDT handles "pending" > breakpoints, i.e. it tried to manage it itself. We set up > stop-on-solib-events so that when DLLs get loaded, we try to set any of > the breakpoints that failed during the main program load. I think gdb is > choking on the solib event handling and you are showing a familiar stack > trace that tells me you've run into the same thing. > > I'll be working on integrating the 6.8 gdb over the next few months and > adding in proper support for gdb's pending breakpoints. In the meantime, > things are kinda broken. > > Cheers, > Doug Schaefer > > > Thanks for the info Doug, I'll use gdb 6.6 instead, it doesn't have this problem with CDT. Good luck with the integration, I hope it doesn't give you too much trouble. :) Rafael |