Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/mips] Stop backtraces when we've lost the PC
Date: Mon, 08 Mar 2004 16:33:00 -0000	[thread overview]
Message-ID: <404CA04A.2070405@gnu.org> (raw)
Message-ID: <20040308163300.eGtoH2YoGdkI_xS177tLFxjXLQLVgPDoerWduIcfmXI@z> (raw)
In-Reply-To: <20040308032324.GA1325@nevyn.them.org>

> This is clone.  It can't be unwound past - there is no stack behind it
> (we're in the child, here).

Briefly, MarkK and I hit a problem with the exact same function on 
GNU/Linux amd64.  The root cause was identified as glibc:
http://sources.redhat.com/ml/gdb-patches/2004-02/msg00567.html

(I'll get to your other follow up but will take a bit of time to digest)

Andrew



  reply	other threads:[~2004-03-08 16:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Daniel Jacobowitz
2004-03-06 23:17 ` Daniel Jacobowitz
2004-03-08  0:56 ` Andrew Cagney
2004-03-08  3:23   ` Daniel Jacobowitz
2004-03-19  0:09     ` Andrew Cagney [this message]
2004-03-08 16:33       ` Andrew Cagney
2004-03-19  0:09     ` Daniel Jacobowitz
2004-03-08 15:48       ` Daniel Jacobowitz
2004-03-08 20:26       ` Daniel Jacobowitz
2004-03-19  0:09         ` Daniel Jacobowitz
2004-03-19  0:09         ` Andrew Cagney
2004-03-17 22:11           ` Andrew Cagney
2004-03-22 21:07           ` Daniel Jacobowitz
2004-03-11 20:51       ` Andrew Cagney
2004-03-19  0:09         ` Andrew Cagney
2004-03-19  0:09         ` Daniel Jacobowitz
2004-03-11 20:57           ` Daniel Jacobowitz
2004-03-19  0:09           ` Andrew Cagney
2004-03-11 23:47             ` Andrew Cagney
2004-03-19  0:09             ` Daniel Jacobowitz
2004-03-12  0:00               ` Daniel Jacobowitz
2004-03-19  0:09       ` Daniel Jacobowitz
2004-03-08 17:41         ` Daniel Jacobowitz
2004-03-19  0:09     ` Daniel Jacobowitz
2004-03-19  0:09   ` Andrew Cagney

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=404CA04A.2070405@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@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