From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Michael Eager <eager@eagercon.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Support for Xilinx MicroBlaze
Date: Thu, 15 Oct 2009 18:31:00 -0000 [thread overview]
Message-ID: <20091015183116.GE5272@adacore.com> (raw)
In-Reply-To: <m3oco8wn3y.fsf@fleche.redhat.com>
> In fact I'd be interested to hear how gdb has dealt with this problem in
> the past. I'm also sure this won't be the last time we're in this
> situation.
As far as I know, we have been trying to be accomodating, but not at
the cost of doing the wrong thing. This should have been fixed in
the compiler since the beginning, but now users are stuck between
a rock and a hard place. I don't know much how CIEs are processed
in GDB, so I don't know offhand how we can provide any kind of info
back to the CIE consumer in mb-tdep.
--
Joel
next prev parent reply other threads:[~2009-10-15 18:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 16:32 Michael Eager
2009-10-15 16:44 ` Tom Tromey
2009-10-15 16:47 ` Joel Brobecker
2009-10-15 18:00 ` Tom Tromey
2009-10-15 18:04 ` Tom Tromey
2009-10-15 18:31 ` Joel Brobecker [this message]
2009-10-16 12:53 ` Daniel Jacobowitz
2009-10-16 16:14 ` Michael Eager
2009-10-15 17:12 ` Michael Eager
2009-10-15 17:18 ` Joel Brobecker
2009-10-15 18:06 ` Michael Eager
2009-10-15 16:46 ` Joel Brobecker
2009-10-15 17:14 ` Michael Eager
2009-10-15 19:31 ` Michael Eager
2009-10-16 7:53 ` Build-failure from " Pierre Muller
2009-10-16 15:56 ` Michael Eager
2009-10-16 16:11 ` Pierre Muller
2009-10-16 16:35 ` Joel Brobecker
2009-10-16 23:21 ` Michael Eager
-- strict thread matches above, loose matches on Subject: below --
2009-10-06 1:35 Michael Eager
2009-10-06 7:14 ` Eli Zaretskii
2009-10-14 1:47 ` Joel Brobecker
2009-10-14 17:49 ` Michael Eager
2009-10-14 17:56 ` Daniel Jacobowitz
2009-10-14 18:01 ` Michael Eager
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=20091015183116.GE5272@adacore.com \
--to=brobecker@adacore.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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