From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [patch] Suggest fixing your target for gdbserver(1)
Date: Mon, 02 Oct 2006 15:55:00 -0000 [thread overview]
Message-ID: <20061002155541.GA5816@nevyn.them.org> (raw)
In-Reply-To: <20060926153331.GA15759@nevyn.them.org>
On Tue, Sep 26, 2006 at 11:33:31AM -0400, Daniel Jacobowitz wrote:
> On Tue, Sep 26, 2006 at 05:27:15PM +0200, Jan Kratochvil wrote:
> > Hi,
> >
> > x86_64 defaults (by bfd matching) to target "i386" instead of its native
> > "i386:x86_64". Therefore if you connect to gdbserver(1) without any `file' or
> > `set architecture' command before the communication will crash on a different
> > expected register sizes.
> >
> > As implementing architecture negotiation is complicated due to gdbserver(1) not
> > being aware of bfd-compatible name of its target and also it may be also
> > unclear to automatically change the target while working remotely it is just
> > suggesting to double-check which architecture you are using.
>
> As a matter of fact I'm implementing automatic detection of 32-bit vs
> 64-bit targets based on the size of register responses right now.
> I hope to have it done later in the week, though it will be tricky
> to break it apart from the rest of my patches for merging.
Just to keep you updated: I got this working on Saturday. I'm still
trying to figure out how to merge it without dragging in all the rest
of this source tree. I'll post some more about that later today.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-10-02 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 15:27 Jan Kratochvil
2006-09-26 15:33 ` Daniel Jacobowitz
2006-10-02 15:55 ` Daniel Jacobowitz [this message]
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=20061002155541.GA5816@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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