From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] New GDB target iq2000
Date: Fri, 04 Mar 2005 16:01:00 -0000 [thread overview]
Message-ID: <20050304160135.GA2264@nevyn.them.org> (raw)
In-Reply-To: <20050304155127.GH2839@cygbert.vinschen.de>
On Fri, Mar 04, 2005 at 04:51:27PM +0100, Corinna Vinschen wrote:
> On Mar 4 10:06, Daniel Jacobowitz wrote:
> > On Fri, Mar 04, 2005 at 04:01:29PM +0100, Corinna Vinschen wrote:
> > > All three cases don't look like simple coincidence. In all three cases
> > > we suffer from either optimized code or unavailable debug information.
> > > The target specific "knowledge", which is represented by the call to
> > > iq2000_scan_prologue helps to master this situation.
> >
> > Would you mind posting disassembly, line table (readelf -wl), and GDB
> > transcript for these failures?
>
> Sure. First the both break.exp fails, which are interlocked:
Thanks! I don't quite grok this bit:
> - Disassembly of function marker4:
>
> 80000368 <marker4>:
> 80000368: 27 bd ff f0 addiu r29,r29,0xfff0
> break marker4^M
> Breakpoint 2 at 0x800001f0: file testsuite/gdb.base/break1.c, line 43.^M
The PCs don't match - I haven't been able to work out how the one
input produced the other output yet.
Let me try something different, which will hopefully waste less of your
time. Could you mail me the two binaries, and the patch to use
skip_prologue_using_sal? I can build an iq2000 GDB easily enough; I
just don't want to set up an entire iq2000 toolchain.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-04 16:01 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 [this message]
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
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=20050304160135.GA2264@nevyn.them.org \
--to=drow@false.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