From: Stefan Weil <sw@weilnetz.de>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
gdb@sourceware.org
Subject: Re: [PATCH v2] tcg/i386: Use GDB JIT debugging interface only for hosts with ELF
Date: Sat, 14 Apr 2012 20:59:00 -0000 [thread overview]
Message-ID: <4F89E518.10801@weilnetz.de> (raw)
In-Reply-To: <4F89A8F7.9090701@twiddle.net>
Am 14.04.2012 18:42, schrieb Richard Henderson:
> On 04/07/2012 11:53 AM, Stefan Weil wrote:
>> Not all i386 / x86_64 hosts use ELF.
>> Ask the compiler whether ELF is used.
>>
>> On w64, gdb crashes when ELF_HOST_MACHINE is defined.
>
> Hmm. Because the other way this could be addressed is
> to fix gdb. (1) it shouldn't crash and (2) it could
> support elf alongside pe-coff fairly easily i'd imagine;
> just a matter of enabling that bfd backend.
>
> Shall we ask gdb maintainers?
>
>
> r~
Fixing problems at their source - in this
case fixing gdb - is of course the best solution.
For the w64 port of gdb, I needed a quick solution.
Usually it will take some time to ask the gdb maintainers,
find a solution, get distributions which include the solution
and use such distributions everywhere.
I don't think that the setup with pe-coff (when it is supported)
will be 100 % identical to the elf setup, so most probably we'll
need a test for ELF / not ELF anyway.
Therefore I suggest to apply my patch, even it is only an
intermediate solution for the next year.
Regards,
Stefan W.
different
next prev parent reply other threads:[~2012-04-14 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1333813984-1516-1-git-send-email-sw@weilnetz.de>
2012-04-14 16:42 ` Richard Henderson
2012-04-14 20:59 ` Stefan Weil [this message]
2012-04-14 21:01 ` [Qemu-devel] " Stefan Weil
[not found] ` <4F89E518.10801__47601.7568879344$1334437169$gmane$org@weilnetz.de>
2012-04-16 18:35 ` Tom Tromey
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=4F89E518.10801@weilnetz.de \
--to=sw@weilnetz.de \
--cc=blauwirbel@gmail.com \
--cc=gdb@sourceware.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).