I have the following problem under Linux version 2.2.12-20 #1 and using g++ --version egcs-2.91.66: When I try to debug a threadaed program (C++) under gdb4.18 gdb crashes while loading the program (i.e, gdb program produces a core dump before a command prompt is generated). When I try GDB5 gdb5 --version GNU gdb 5.0 Copyright 2000 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu". -- and type run this happens: . . [New Thread 2049 (runnable)] [New Thread 1026 (runnable)] [New Thread 2051 (runnable)] [New Thread 3076 (runnable)] [New Thread 4101 (runnable)] [New Thread 5126 (runnable)] [New Thread 6151 (runnable)] [New Thread 7176 (runnable)] [New Thread 8201 (runnable)] [New Thread 9226 (runnable)] [New Thread 10251 (runnable)] [New Thread 11276 (runnable)] [New Thread 12301 (runnable)] Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread 11276 (runnable)] 0x0 in ?? () Current language: auto; currently c (gdb) where #0 0x0 in ?? () ---- It this a known problem with GDB under Linux ? Thanks, Alan _______________________________________________ Bug-gdb mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gdb
