From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6406 invoked by alias); 23 Apr 2002 22:49:33 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6287 invoked from network); 23 Apr 2002 22:49:27 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 23 Apr 2002 22:49:27 -0000 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17095w-00086y-00; Tue, 23 Apr 2002 18:49:08 -0400 Date: Tue, 23 Apr 2002 15:49:00 -0000 From: Daniel Jacobowitz To: Bino Mathew Cc: bug-gdb@gnu.org, bug-glibc@gnu.org, libc-alpha@sources.redhat.com, gdb@sources.redhat.com Subject: Re: Regarding Libc,threaded application on mips-linu Message-ID: <20020423184908.A31117@nevyn.them.org> Mail-Followup-To: Bino Mathew , bug-gdb@gnu.org, bug-glibc@gnu.org, libc-alpha@sources.redhat.com, gdb@sources.redhat.com References: <3CC53B59.B08FD5C4@wipro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CC53B59.B08FD5C4@wipro.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2002-04/txt/msg00405.txt.bz2 On Tue, Apr 23, 2002 at 04:15:45PM +0530, Bino Mathew wrote: > Hi All, > I am using a linux(2.4.16) on mips (bigendian) box for development of > gdb > tool.Recently I downloaded gdb 5.1 source code and was able to > successfully configure and > compile for the above mentioned mips box.I am also encountering the same > old > problem of debugging the threaded application... > > Starting program: /data/gdb/./SimpleVideolin.out > [New Thread 1024 (LWP 438)] > > Program received signal SIGTRAP, Trace/breakpoint trap. > [Switching to Thread 1024 (LWP 438)] > 0x00000000 in ?? () > > In one of the mailing list I saw that this due to bug in libc. > Can you tell me > 1.Where can find the libc which don't have this bug In CVS. It has not been released. 2.3 should contain the fixes. > 2.Is there any patches are associated with gdb for above mentioned > problem No, none are needed. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer