From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: brobecker@adacore.com (Joel Brobecker), gdb-patches@sourceware.org
Subject: Re: [RFC] Reducing the use of current_language - some patches
Date: Mon, 05 Nov 2007 15:25:00 -0000 [thread overview]
Message-ID: <200711051525.lA5FPDPo030827@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20071105131905.GA26912@caradoc.them.org> from "Daniel Jacobowitz" at Nov 05, 2007 08:19:05 AM
Daniel Jacobowitz wrote:
> On Sun, Nov 04, 2007 at 07:50:14PM -0800, Joel Brobecker wrote:
> > On the other hand, I'm not sure we're ready to have the parse context
> > contain the gdbarch. For instance, the breakpoint structure doesn't
> > save it, so we don't have access to it when we want to re_set the
> > breakpoint.
>
> I suspect we'd want to re-set with the current gdbarch anyway. The
> old one may no longer apply...
On the other hand, once we support multi-architecture debugging in
a single session, we will certainly have to distinguish between
breakpoints set in code with different architectures. That's one
of the hacks in the Cell combined debugger today ...
I'm not completely sure on what the correct solution is, maybe it
can be as simple as checking the gdbarch associated with the
objfile where the breakpoint is set (assuming we will get per-
objfile gdbarchs at some point).
In any case, as long as the changes Joel implements use something
like a "parse context" structure to pass around, it should be
simple to extend that with a gdbarch if and when we want to solve
the multi-arch problem.
For now, it's probably indeed best to leave it out.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-11-05 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 10:47 Joel Brobecker
2007-11-04 17:15 ` Ulrich Weigand
2007-11-05 3:50 ` Joel Brobecker
2007-11-05 13:19 ` Daniel Jacobowitz
2007-11-05 15:25 ` Ulrich Weigand [this message]
2007-11-05 17:18 ` Joel Brobecker
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=200711051525.lA5FPDPo030827@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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