From: Andrew Cagney <ac131313@redhat.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: [RFC] target defined OSABI sniffer
Date: Thu, 26 Jun 2003 15:50:00 -0000 [thread overview]
Message-ID: <3EFB1542.3020308@redhat.com> (raw)
In-Reply-To: <040001c33bf1$4ed98060$0202040a@catdog>
> It seems that a lot of effort has been put into the multi-arch stuff but
> most of it centers around recognizing a binary and setting things up based
> on that. I'm pondering whether that is the right approach in all cases.
> Shouldn't the target be telling gdb what it should be doing rather than the
> other way around?
Yes.
Will need to read the rest of your e-mail later :-( BTW, there's also:
http://sources.redhat.com/gdb/papers/multi-arch/real-multi-arch/index.html#SEC40
as a second discussion point.
Andrew
next prev parent reply other threads:[~2003-06-26 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 14:43 Kris Warkentin
2003-06-26 14:46 ` Daniel Jacobowitz
2003-06-26 15:50 ` Andrew Cagney [this message]
2003-06-26 18:56 ` Kris Warkentin
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=3EFB1542.3020308@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).