Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA/hppa] unwind pc in bottom frame using correct register
Date: Sat, 04 Dec 2004 10:53:00 -0000	[thread overview]
Message-ID: <20041204084624.GS6359@tausq.org> (raw)
In-Reply-To: <20041204075101.GS16491@adacore.com>

> Almost works. We get the first frame right, but then the backtraces
> are broken because we get identical frames. This sort of makes sense
> to me, since once you are past frame 0, you know which register to
> unwind by inspecting the function associated to the frame (either prologue
> analysis, or using the unwind info, or ...). No? So I would venture
> that the SS_INSYSCALL thingy might be specific to the innermost frame?

hrm, yes.... you are right.

> > the bit about HPPA_FLAG_REGNUM seems to be an hpux specific thing. I
> > think the syscall stub does something special so we try to return r31
> > instead of pcoqh. I haven't looked at this in detail...
> 
> If it's HP/UX specific, it must be hurting hppa-linux?

well, on hppa-linux the "flags" register is always 0, so we always read
pcoqh.

as you said i think we need to first better understand what is this
SS_INSYSCALL thing....

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/


  reply	other threads:[~2004-12-04  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04  5:31 Joel Brobecker
2004-12-04  7:51 ` Randolph Chung
2004-12-04  8:46   ` Joel Brobecker
2004-12-04 10:53     ` Randolph Chung [this message]
2004-12-04 12:42       ` Mark Kettenis
2004-12-08  4:33         ` Randolph Chung
2004-12-08  8:21           ` Randolph Chung
2004-12-08 22:20             ` Mark Kettenis

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=20041204084624.GS6359@tausq.org \
    --to=randolph@tausq.org \
    --cc=brobecker@adacore.com \
    --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