Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Mark Kettenis <kettenis@gnu.org>
Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA/hppa] unwind pc in bottom frame using correct register
Date: Wed, 08 Dec 2004 04:33:00 -0000	[thread overview]
Message-ID: <20041208032725.GI6359@tausq.org> (raw)
In-Reply-To: <200412041126.iB4BQsd8000662@elgar.sibelius.xs4all.nl>

> Anyway, the problems Joel sees can be fixed by explicitly setting
> "flags" to zero in all unwound frames.  This somehow seems the correct
> approach since this "flags" register is only meaningful in the
> sentinel frame.  This is implemented by the attached patch (wich will
> no longer apply after Randolph's recent change, but you get the idea).

hrm, something is broken. on hppa64-hp-hpux11.11 this is causing a lot
of unwinding failures. the hpux unwind_pc method is getting flags that
have the magic "2" bit set, so it gets the pc from 31 instead of the
pcoqh register.

i don't quite yet understand why this is happening. if i do "print
$flags" on frame #0 the value seems reasonable.

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


  reply	other threads:[~2004-12-08  3:27 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
2004-12-04 12:42       ` Mark Kettenis
2004-12-08  4:33         ` Randolph Chung [this message]
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=20041208032725.GI6359@tausq.org \
    --to=randolph@tausq.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@gnu.org \
    /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