From: Tom Tromey <tromey@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Richard Henderson <rth@twiddle.net>,
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: Mon, 16 Apr 2012 18:35:00 -0000 [thread overview]
Message-ID: <87bomr1sfl.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F89E518.10801__47601.7568879344$1334437169$gmane$org@weilnetz.de> (Stefan Weil's message of "Sat, 14 Apr 2012 22:59:04 +0200")
>>>>> "Stefan" == Stefan Weil <sw@weilnetz.de> writes:
Stefan> Fixing problems at their source - in this
Stefan> case fixing gdb - is of course the best solution.
Could you file a gdb bug report?
Tom
prev parent reply other threads:[~2012-04-16 18:35 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
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 [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=87bomr1sfl.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=gdb@sourceware.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sw@weilnetz.de \
/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).