From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16856 invoked by alias); 11 Jul 2007 08:27:38 -0000 Received: (qmail 16847 invoked by uid 22791); 11 Jul 2007 08:27:37 -0000 X-Spam-Check-By: sourceware.org Received: from smtp9k.poczta.onet.pl (HELO smtp9k.poczta.onet.pl) (213.180.130.89) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 11 Jul 2007 08:27:33 +0000 Received: from pmq4.test.onet.pl ([192.168.246.4]:14468 "EHLO pmq4") by kps9.test.onet.pl with ESMTP id convert rfc822-to-8bit (ORCPT ); Wed, 11 Jul 2007 10:27:22 +0200 Received: from 217.147.104.220 by 192.168.240.103 with HTTP; Wed, 11 Jul 2007 10:27:22 +0200 ,from 175.28.12.111 by 217.147.104.220 with HTTP Date: Wed, 11 Jul 2007 08:27:00 -0000 From: m.sikorski0@poczta.onet.pl To: gdb@sourceware.org Subject: Remote mutli-threaded debugging with large number of threads X-Mailer: onet.poczta Message-Id: MIME-Version: 1.0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8BIT Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-07/txt/msg00090.txt.bz2 Hello, I faced recently strange issue using remote gdb debugging (cross i386-ppc). With ~60 threaded application debugging does not work well. Info threads returns incomplete information: (gdb) info threads 60 Thread 2150 0x00000000 in ?? () 59 Thread 2151 0x00000000 in ?? () 58 Thread 2152 0x00000000 in ?? () 57 Thread 2153 0x00000000 in ?? () 56 Thread 2155 0x00000000 in ?? () 55 Thread 2156 0x00000000 in ?? () 54 Thread 2157 0x00000000 in ?? () ... Problem does not exist when I try to debug ~17 threaded application, and debugging works fine with the same cross-configuration: (gdb) info threads 17 Thread 8563 0x0f211518 in do_sigwaitinfo () from /tftpboot/nfs/lib/tls/libc.so.6 16 Thread 8564 0x0f93670c in sem_wait@GLIBC_2.0 () from /tftpboot/nfs/lib/tls/libpthread.so.0 15 Thread 8565 0x0f93670c in sem_wait@GLIBC_2.0 () from /tftpboot/nfs/lib/tls/libpthread.so.0 14 Thread 8566 0x0f934264 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /tftpboot/nfs/lib/tls/libpthread.so.0 13 Thread 8567 0x0f933ea8 in pthread_cond_wait@@GLIBC_2.3.2 () from /tftpboot/nfs/lib/tls/libpthread.so.0 12 Thread 8568 0x0f29ca4c in ?? () from /tftpboot/nfs/lib/tls/libc.so.6 11 Thread 8569 0x0f934264 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /tftpboot/nfs/lib/tls/libpthread.so.0 ... Also when I'm usling local gdb and attach to ~60 threaded application info threads shows correct output, so problem does not exist. Is this a bug or still something is misconfigured? My environment: GDB 6.6 gdbserver on ppc gdb on i386-linux or i386-cygwin (on both results are the same 17 threads work fine, 60 are having problem) I'm also using this with Eclipse with great results on 17 threads while in 60 threads after hitting breakpoint stepping is really slow and practically does not work. Regards Maciej Sikorski