From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: [rfa] std-regs.c, value_of_builtin_frame_pc_reg, don't bother checking for null frame.
Date: Tue, 01 Mar 2011 21:40:00 -0000 [thread overview]
Message-ID: <201103012139.59726.pedro@codesourcery.com> (raw)
In-Reply-To: <4D6D5B44.9020500@vmware.com>
On Tuesday 01 March 2011 20:47:00, Michael Snyder wrote:
> If frame is null, we will have crashed already from dereferencing it.
Yeah, looks like a left over from before the "there's always
a frame" changes years ago.
> reversenull3.txt
> 2011-03-01 Michael Snyder <msnyder@vmware.com>
>
> * std-regs.c (value_of_builtin_frame_pc_reg): Frame can't be null.
Okay.
--
Pedro Alves
next prev parent reply other threads:[~2011-03-01 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 20:47 Michael Snyder
2011-03-01 21:40 ` Pedro Alves [this message]
2011-03-01 21:47 ` Michael Snyder
2011-03-01 21:52 ` Pedro Alves
2011-03-01 21:56 ` Michael Snyder
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=201103012139.59726.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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