From: Alexandre Oliva <aoliva@redhat.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: Jonathan Larmour <jlarmour@redhat.com>, gdb@sources.redhat.com
Subject: Re: SH breakpoint problem
Date: Tue, 07 Aug 2001 21:54:00 -0000 [thread overview]
Message-ID: <orofprp2x7.fsf@feijoada.lsd.ic.unicamp.br> (raw)
In-Reply-To: <1010807224211.ZM23418@ocotillo.lan>
On Aug 7, 2001, Kevin Buettner <kevinb@cygnus.com> wrote:
> My opinion is that gdb should use the information obtained from
> find_pc_line() only to refine the limit searched by the prologue
> scanner. The prologue scanner needs to be taught that it must
> never scan past an instruction which modifies the flow of control
> (i.e, branch or call instructions).
This would cause a yet-to-be-contributed port I worked on to stop the
search too early, because some peculiarities of the ABI require
function calls to be inserted in the prologue in certain
circumstances.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-08-07 21:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 19:45 Jonathan Larmour
2001-08-07 5:53 ` Jonathan Larmour
2001-08-07 7:26 ` Elena Zannoni
2001-08-07 7:33 ` Jonathan Larmour
2001-08-07 7:54 ` Elena Zannoni
2001-08-07 8:05 ` Jonathan Larmour
2001-08-09 14:49 ` Andrew Cagney
2001-08-09 16:52 ` Jonathan Larmour
2001-08-09 18:05 ` Andrew Cagney
2001-08-10 14:24 ` Jonathan Larmour
2001-08-07 15:42 ` Kevin Buettner
2001-08-07 21:54 ` Alexandre Oliva [this message]
2001-08-07 22:46 ` Kevin Buettner
2001-08-09 12:48 ` Jonathan Larmour
2001-08-09 13:29 ` Kevin Buettner
2001-08-09 14:05 ` Jonathan Larmour
2001-08-09 14:28 ` Andrew Cagney
2001-08-09 14:57 ` Kevin Buettner
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=orofprp2x7.fsf@feijoada.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jlarmour@redhat.com \
--cc=kevinb@cygnus.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