From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: GDB Patches <gdb-patches@sources.redhat.com>, mark.kettenis@xs4all.nl
Subject: Re: [RFA] Take III, part 2: am33 linux corefile support
Date: Wed, 29 Jun 2005 02:14:00 -0000 [thread overview]
Message-ID: <42C20409.9060709@redhat.com> (raw)
In-Reply-To: <20050628014317.GA6950@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Mon, Jun 27, 2005 at 05:40:20PM -0700, Michael Snyder wrote:
>
> Could you explain why you needed a sniffer?
> [...]
> i.e. what's this covering that the generic sniffer won't. I can work
> out the answer to the question in terms of ELF header flags, but I
> assume you've got .note.ABI-tag like other Linux ports do.
I dunno... I've never used this interface before.
I just followed the first example I could find.
Is there a generic sniffer?
next prev parent reply other threads:[~2005-06-29 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 0:41 Michael Snyder
2005-06-28 1:43 ` Daniel Jacobowitz
2005-06-29 2:14 ` Michael Snyder [this message]
2005-06-29 2:16 ` Daniel Jacobowitz
2005-06-28 21:08 ` Mark Kettenis
2005-09-02 23:02 ` Kevin Buettner
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=42C20409.9060709@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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