From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] New method find_frame_sal()
Date: Sat, 30 Nov 2002 21:59:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1021201075842.15364B-100000@is> (raw)
In-Reply-To: <3DE6C819.5040500@redhat.com>
On Thu, 28 Nov 2002, Andrew Cagney wrote:
> While cleaning up accesses to the `struct frame_info', I kept coming
> across code snippits like:
>
> sal = find_pc_line (fi->pc,
> (fi->next != (struct frame_info *) NULL
> && !(get_frame_type (fi->next) == SIGTRAMP_FRAME)
> && !(get_frame_type (fi->next) == DUMMY_FRAME)));
>
> (Originally it was worse, as there was also fi->signal_handler_caller
> and PC_IN_CALL_DUMMY (fi->pc, fi->frame, fi->frame).)
>
> The attached patch adds the function:
>
> find_frame_sal(fi, &sal);
>
> that encapsulates all of the above.
Should this method be documented in gdbint.texinfo perhaps?
next prev parent reply other threads:[~2002-12-01 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 17:51 Andrew Cagney
2002-11-30 21:59 ` Eli Zaretskii [this message]
2002-12-01 11:51 ` 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=Pine.SUN.3.91.1021201075842.15364B-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@redhat.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