From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: deuling@de.ibm.com, gdb-patches@sourceware.org, uweigand@de.ibm.com
Subject: Re: [rfc] [17/17] Get rid of current_gdbarch in go32-nat.c
Date: Wed, 24 Oct 2007 04:08:00 -0000 [thread overview]
Message-ID: <ud4v5rwd1.fsf@gnu.org> (raw)
In-Reply-To: <20071023211528.GA5996@caradoc.them.org> (message from Daniel Jacobowitz on Tue, 23 Oct 2007 17:15:28 -0400)
> Date: Tue, 23 Oct 2007 17:15:28 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Markus Deuling <deuling@de.ibm.com>, gdb-patches@sourceware.org,
> uweigand@de.ibm.com
>
> Even a single-architecture port may have more than one
> current_gdbarch. A gdbarch is fine-grained and e.g. different
> executables can lead to different gdbarches. So a GDB for DJGPP which
> supported debugging two programs at once might need more than one
> "current" gdbarch.
Can you please describe an example where this is possible? Perhaps I
don't understand what is gdbarch, but I think this is impossible with
DJGPP.
next prev parent reply other threads:[~2007-10-24 4:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 8:56 Markus Deuling
2007-10-12 10:56 ` Eli Zaretskii
2007-10-22 7:44 ` Markus Deuling
2007-10-22 20:25 ` Eli Zaretskii
2007-10-23 10:31 ` Markus Deuling
2007-10-23 21:15 ` Eli Zaretskii
2007-10-23 21:55 ` Daniel Jacobowitz
2007-10-24 4:08 ` Eli Zaretskii [this message]
2007-10-24 11:48 ` Daniel Jacobowitz
2007-10-24 19:24 ` Eli Zaretskii
2007-10-24 13:39 ` Ulrich Weigand
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=ud4v5rwd1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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