John Clark wrote:
I built the latest GDB-6.3, as well as rebuilt glibc-2.3.5, and now when
I step through the
main code line, which creates the tasks (I'm using the pthreads.c from
the GDB testsuite), I do
not getany output from:
info threads
When I set a break point on the entry point of one of the
soon-to-be-created threads,
I get a diagnostic message:
Program terminated with signal SIGTRAP, Trace/Breakpoint trap.
The program no longer exists.
Are you sure your glibc and gdb were both configured to support threads
when they were compiled?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
