From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Jacobowitz To: John Van Horne Cc: gdb@sources.redhat.com, jvhorne@cosinecom.com Subject: Re: platform difference with threads -- help Date: Mon, 06 Aug 2001 17:52:00 -0000 Message-id: <20010806175243.A23711@nevyn.them.org> References: <200108070007.RAA15529@guava-lx.eng.cosinecom.com> X-SW-Source: 2001-08/msg00034.html On Mon, Aug 06, 2001 at 05:07:40PM -0700, John Van Horne wrote: > Hi, > > I've got two PowerPC Linux platforms -- one is a G4 Macintosh, the other > is one of my employer's products. Both are running Linux kernel 2.4.2. > But when I run it on the product I get: > > sh-2.03$ uname -a > Linux blade3_pe0.cosine 2.4.2 #45 Mon Aug 6 10:18:17 PDT 2001 ppc unknown > sh-2.03$ ./gdb gdb_thread_test > GNU gdb 20010627 > Copyright 2001 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 "powerpc-unknown-linux-gnu"... > (gdb) run > Starting program: /home/sharc/gdb_thread_test > > Program received signal SIG32, Real-time event 32. > 0x0fedf224 in __syscall_rt_sigsuspend () from /lib/libc.so.6 > (gdb) > > I can continue passed this until: > > (gdb) c > Continuing. > > Program received signal SIGSEGV, Segmentation fault. > 0x0fedf224 in __syscall_rt_sigsuspend () from /lib/libc.so.6 > (gdb) > > > Can anyone help me figure out why the behavior is different on the two > platforms? The kernel > version is the same. The test program is the same, and the GDB is the same. > I also have the > same libraries on both platforms. Do you really? Is there a libthread_db installed on your target system? This looks as if the thread module is not initialized. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer