On Wednesday 17 September 2008 20:14:52, Pawel Veselov wrote: > I get this every now and then on some "stuck" applications: > > Program received signal SIGTRAP, Trace/breakpoint trap. > 0x8001b6ec in ?? () > (gdb) where > #0 0x8001b6ec in ?? () > (gdb) info threads > * 1 Thread 1154900630 0x8001b6ec in ?? () > warning: Couldn't restore frame in current thread, at frame 0 > 0x8001b6ec in ?? ()
Ok, is it always the same address? It's been a while, but I think you get that when the thread is stuck inside a system call. If so, I don't expect this to be worse than what it was with the older gdb in our tree, and we do need to teach GDB how to unwind passed that. -- Pedro Alves ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel