From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] New GDB target iq2000
Date: Sat, 05 Mar 2005 20:20:00 -0000 [thread overview]
Message-ID: <20050305202034.GA15313@nevyn.them.org> (raw)
In-Reply-To: <200503052017.j25KHjOK016915@elgar.sibelius.xs4all.nl>
On Sat, Mar 05, 2005 at 09:17:45PM +0100, Mark Kettenis wrote:
> Date: Sat, 5 Mar 2005 14:37:39 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> > That suggestion has been made more than once in the past; I don't
> > really consider this viable for architectures where instructions
> > aren't fixed length.
>
> Could you explain why that particular property makes a difference?
>
> Makes it difficult to ignore instructions; GDB has to know the length
> of them in order to skip them.
Trivial, even in the existing framework - ask the disassembler. A
complete GDB port may not have a simulator, let alone my hypothetical
uber-simulator, but it will definitely have a disassembler.
> > Anyway, I think most problems are caused because we are trying to use
> > the same code for two distinct cases: (a) getting an upper limit for
> > the prologue end and (b) getting a lower limit for the prologue end.
> > Combining (a) and (b) results in having to determine the end of the
> > prologue exactly, which is much harder.
>
> Just checking, but first-line breakpoints should go at the lower limit
> and scanning until the upper limit - is that right?
>
> Yup. Although the lower-limit for first-line breakpoints may cause
> bogus parameter values to be printed. I consider that less a problem
> than my program unexpectedly running to completion though. The
> problem is that some people tend to think differently and we never
> reached consensus about it.
Well, it makes sense to me. It's clear that the FRV and submitted
iq2000 ports have different heuristics for these two cases; it would be
good to cover both of them in common code.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-05 20:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 16:35 Corinna Vinschen
2005-03-01 22:13 ` Jim Blandy
2005-03-01 22:19 ` Daniel Jacobowitz
2005-03-02 9:08 ` Corinna Vinschen
2005-03-03 17:34 ` Daniel Jacobowitz
2005-03-03 17:46 ` Kevin Buettner
2005-03-03 17:51 ` Daniel Jacobowitz
2005-03-03 19:17 ` Kevin Buettner
2005-03-04 9:46 ` Corinna Vinschen
2005-03-04 14:14 ` Daniel Jacobowitz
2005-03-04 15:01 ` Corinna Vinschen
2005-03-04 15:06 ` Daniel Jacobowitz
2005-03-04 15:51 ` Corinna Vinschen
2005-03-04 16:01 ` Daniel Jacobowitz
2005-03-04 22:01 ` Daniel Jacobowitz
2005-03-05 11:29 ` Mark Kettenis
2005-03-05 16:44 ` Daniel Jacobowitz
2005-03-05 18:13 ` Mark Kettenis
2005-03-05 19:37 ` Daniel Jacobowitz
2005-03-05 20:18 ` Mark Kettenis
2005-03-05 20:20 ` Daniel Jacobowitz [this message]
2005-03-07 10:08 ` Corinna Vinschen
2005-03-07 14:05 ` Daniel Jacobowitz
2005-03-07 20:17 ` Corinna Vinschen
2005-03-07 20:37 ` Daniel Jacobowitz
2005-03-08 9:00 ` Corinna Vinschen
2005-03-08 13:32 ` Daniel Jacobowitz
2005-03-07 21:32 ` Daniel Jacobowitz
2005-03-07 21:35 ` Daniel Jacobowitz
2005-03-08 9:00 ` Corinna Vinschen
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=20050305202034.GA15313@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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