From: Randolph Chung <randolph@tausq.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] Fix unwind handling for hppa
Date: Sat, 17 Apr 2004 16:43:00 -0000 [thread overview]
Message-ID: <20040417172027.GD17842@tausq.org> (raw)
In-Reply-To: <20040417163525.GA3521@nevyn.them.org>
> > + if (frame_relative_level (next_frame) >= 0 ||
> > + frame_pc_unwind (next_frame) >=
> > + hppa_skip_prologue (frame_func_unwind (next_frame)))
>
> - your formatting is wrong; operators always come at the beginning
> of the line.
ok, i have to go and read the coding style doc some more since it is
very different from what i'm used to :)
> - Checking the frame level is wrong. It's wrong both in practice and
> in principle: in practice, the next frame could be a dummy frame
> or a signal frame. There's a test case in the testsuite which
> covers this.
mmmm, ok. so if i just do:
if (frame_pc_unwind (next_frame)
>= hppa_skip_prologue (frame_func_unwind (next_frame)))
then it's ok? or is there a more efficient/correct mechanism to get to
this info?
thanks,
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2004-04-17 16:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 7:32 Randolph Chung
2004-04-17 16:35 ` Daniel Jacobowitz
2004-04-17 16:43 ` Randolph Chung [this message]
2004-04-17 16:54 ` Daniel Jacobowitz
2004-04-17 18:13 ` Randolph Chung
2004-04-21 14:55 ` Andrew Cagney
2004-04-21 15:18 ` Randolph Chung
2004-04-21 21:53 ` Andrew Cagney
2004-04-22 0:06 ` Randolph Chung
2004-04-22 0:49 ` Andrew Cagney
2004-04-22 2:38 ` Randolph Chung
2004-04-22 2:54 ` Randolph Chung
2004-04-22 3:00 ` Randolph Chung
2004-04-22 19:27 ` Andrew Cagney
2004-04-23 3:12 ` Randolph Chung
2004-04-23 3:40 ` Daniel Jacobowitz
2004-04-24 0:03 ` 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=20040417172027.GD17842@tausq.org \
--to=randolph@tausq.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