From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.14-5.0-bigphys i686)
Description of problem:
when running a multi-threaded program under gdb I get an assertion failure:
lin-lwp.c:409: gdb-internal-error: resume_callback: Assertion `lp->step'
An internal GDB error was detected. This may make further
debugging unreliable. Continue this debugging session? (y or n)
Steps to Reproduce:
1. I don't have a standalone example that reproduces this. I'm running a
program that I'm developing. It starts by creating 256 threads and in
thoses threads there are some mallocs and frees.
Actual Results: gdb assertion failure
Expected Results: No assertion failure
I see the assertion failure when I step through the code with gdb. Not
sure if it happens when not stepping
Which version of gdb?
(BTW: The 5.0rh-9 RPMs at http://people.redhat.com/teg/gdb/ (and soon/already in
Rawhide) has lots of fixes for threads).
This is was from gdb-5.0rh-8, but I also pulled the latest gdb snapshot,
gdb+dejagnu-20010523, and the problem still occurs.
Can you try this on a RHL 7.1 system, to see if glibc and kernel makes a
difference? The 5.0rh-9 no longer has a limit of maximum 32 threads to debug...
If this doesn't work, a test case is essential.
Closed due to lack of reproducible testcase. Reopen if one becomes available.