Messages in this thread | | | Date | Wed, 18 May 2005 17:36:17 -0700 | From | Ajay Patel <> | Subject | Re: GDB, pthreads, and kernel threads |
| |
I have an exactly same problem. My platform is PPC, Linux 2.6.11.4, glibc 2.3.4 with linux threads.
One thing I observed that the problem only occurs when break point is set in non-main thread.
Thanks Ajay
On 5/18/05, Robert Hancock <hancockr@shaw.ca> wrote: > 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 hancockr@nospamshaw.ca > Home Page: http://www.roberthancock.com/ > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |