Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: fnf@specifix.com, gdb-patches@sourceware.org
Subject: Re: [RFA] Don't try to run auxv tests in simulator
Date: Fri, 12 May 2006 20:48:00 -0000	[thread overview]
Message-ID: <200605122032.k4CKWfst002737@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060511124149.GB3086@nevyn.them.org> (message from Daniel 	Jacobowitz on Thu, 11 May 2006 08:41:49 -0400)

> Date: Thu, 11 May 2006 08:41:49 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Thu, May 11, 2006 at 05:45:35AM -0400, Fred Fish wrote:
> > AFAIK all available simulators don't support auxv info, so trying to
> > run the auxv tests will fail.  They also need corefile support.
> > 
> > I see that corefile.exp has:
> > 
> >   # are we on a target board
> >   if ![isnative] then {
> >       return
> >   }
> > 
> > which may be too restrictive for auxv.  So I'd propose suppressing the
> > auxv tests just for simulators, for now at least.
> > 
> > 2006-05-11  Fred Fish  <fnf@specifix.com>
> > 
> > 	* gdb.base/auxv.exp: Simulators don't support auxv info
> > 	so don't run test if executing in a simulator.
> 
> Simulatorness has nothing to do with it, though.  Does anyone know if
> the BSDs use auxv, or is it entirely a GNU/Linux + Solaris thing?

GDB doesn't have any auxv support on OpenBSD.  There is some minimal
auxv stuff in the kernel (just enough to implement stuff in the
official ELF ABI), but it isn't really interesting, and there is no
way for the debugger to get at it.  I have no plans to implement it.
I think the situation is similar for the other BSDs.

Mark


      parent reply	other threads:[~2006-05-12 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11  9:44 Fred Fish
2006-05-11 12:41 ` Daniel Jacobowitz
2006-05-11 13:13   ` Fred Fish
2006-05-11 13:08     ` Daniel Jacobowitz
2006-05-11 17:38   ` Nathan J. Williams
2006-05-12 20:48   ` Mark Kettenis [this message]

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=200605122032.k4CKWfst002737@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=fnf@specifix.com \
    --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