Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Bino Mathew <bino.mathew@wipro.com>
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
Date: Tue, 23 Apr 2002 15:49:00 -0000	[thread overview]
Message-ID: <20020423184908.A31117@nevyn.them.org> (raw)
In-Reply-To: <3CC53B59.B08FD5C4@wipro.com>

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


      parent reply	other threads:[~2002-04-23 22:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23  3:40 Bino Mathew
2002-04-23 11:40 ` H . J . Lu
2002-04-23 15:49 ` Daniel Jacobowitz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020423184908.A31117@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=bino.mathew@wipro.com \
    --cc=bug-gdb@gnu.org \
    --cc=bug-glibc@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=libc-alpha@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox