This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Assert in linux_nat_resume

Daniel Jacobowitz wrote:
On Tue, Aug 12, 2008 at 03:21:40PM -0400, Marc Ferland wrote:
I'm pretty sure it has something to do with my program but I don't know where to start (Debugging with printf() is a rather tedious task!). Any help would be greatly appreciated.

The first thing to try is definitely a snapshot of current CVS GDB.

I tried with seems to have a similar problem.

[New LWP 29169]
linux-nat.c:1669: internal-error: linux_nat_resume: Assertion `lp != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

After further testing, this seems to happen only when I have a breakpoint somewhere inside a thread. The first time I hit the breakpoint everything is fine. But if I exit a thread and recreate it, I get the previously mentioned message.

I also found a workaround:
- The first time I hit the breakpoint, I delete it;
- I place a breakpoint on the pthread_join() call for this thread;
- When I break on the pthread_join() call, I recreate the breakpoint inside the thread;

This way, I'm able to break inside the thread every time I create it (pthread_create()).


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]