public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: "Kris Warkentin" <kewarken@qnx.com>
Cc: Richard.Earnshaw@arm.com, "Kevin Buettner" <kevinb@redhat.com>,
	"Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: problem with fetch_link_map_offsets
Date: Tue, 10 Jun 2003 12:26:00 -0000	[thread overview]
Message-ID: <200306101226.h5ACQOs02766@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Tue, 10 Jun 2003 08:21:30 EDT." <047001c32f4a$d31eead0$0202040a@catdog>

> > > Yeah but....a QNX binary is just an ordinary elf binary.  There are no
> > > special sections or magic in there for the sniffer to catch.  Hence my
> > > problem.  Perhaps it should be returning unknown so that another sniffer
> > > (like my one liner) could get it?
> > >
> >
> > NetBSD binaries look like ordinary ELF too, as do Linux.  The only way to
> > resolve this is to arange for the crt0.o file to contain some magic that
> > GDB can find.  Normally this is a special .note section.
> >
> > Can you not arrange for QNX binaries to have such a note and then add
> that.
> 
> Perhaps.  I'll have to talk to some of the folk here.  I think it would be
> really handy to be able to recognize one of our binaries.  Thanks for the
> suggestion.
> 

The note has other uses, too.  For example, it can be used to ensure that 
the kernel doesn't run applications that are intended for another 
platform, or to enable an emulation mode if running such an app, or even 
to give backwards compatibility if the kernel/user ABI changes.

R.

  reply	other threads:[~2003-06-10 12:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-28 20:21 Kris Warkentin
2003-04-28 21:23 ` Andrew Cagney
2003-04-29 13:27   ` Kris Warkentin
2003-04-29 15:07 ` Kevin Buettner
2003-04-29 15:25   ` Kris Warkentin
2003-04-29 16:28     ` Kevin Buettner
2003-04-29 21:18       ` Kris Warkentin
2003-06-09 21:20         ` Kris Warkentin
2003-06-09 21:34           ` Kevin Buettner
2003-06-09 21:40             ` Kris Warkentin
2003-06-10 10:12               ` Richard Earnshaw
2003-06-10 12:21                 ` Kris Warkentin
2003-06-10 12:26                   ` Richard Earnshaw [this message]
2003-06-10 14:53                   ` Kris Warkentin
2003-06-11 19:05                     ` 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=200306101226.h5ACQOs02766@pc960.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@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).