Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: [RFC] TARGET_OBJECT_WCOOKIE
Date: Sun, 01 Feb 2004 20:23:00 -0000	[thread overview]
Message-ID: <20040201202313.GA20053@nevyn.them.org> (raw)
In-Reply-To: <200402011702.i11H2HEZ000487@elgar.kettenis.dyndns.org>

On Sun, Feb 01, 2004 at 06:02:17PM +0100, Mark Kettenis wrote:
> Actually the purpose of this RFC is twofold.
> 
> First, I'd like to add a TARGET_OBJECT_WCOOKIE method to support the
> StackGhost cookie on OpenBSD/sparc.  This really is something
> target-related rather than OS/ABI related.  GDB will have to deal with
> StackGhost when running non-OpenBSD binaries on an OpenBSD kernel.
> Moreover, older OpenBSD kernels might not have StackGhost.  Anyway,
> are there objections to adding something like the attached patch?

Not from me.

> The second issue I'd like your opinion on is related to the patch.  I
> followed the example set by TARGET_OBJECT_UNWIND_TABLE in having a
> macro (NATIVE_XFER_WCOOKIE) to invoke the native-specific function
> that fetches the cookie.  This macro would be defined in the nm.h
> file, but wasn't it our goal to get rid of the nm.h file sooner rather
> than later?  Shouldn't we add another method for these kinds of hooks?
> The obvious alternatives are:
> 
> a) Use a public function pointer, which is initialized to some
>    do-nothing-and-return-minus-one function by default.  This function
>    pointer would be overridden by some code in the appropraite *-nat.c
>    files.
> 
> b) Use a private function pointer, and provide a function to set that
>    pointer, along the lines of inftarg_set_find_memory_regions().
> 
> Opinions?

Personally, I think the -nat files should have a chance to edit
child_ops, or provide their own version of child_ops.  This would
eliminate 90% of the gunk in nm* files which is checked in the various
inf* files implementing child_ops.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-01 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01 17:02 Mark Kettenis
2004-02-01 20:23 ` Daniel Jacobowitz [this message]
2004-02-02 19:01   ` Andrew Cagney
2004-02-02 19:26     ` Daniel Jacobowitz

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=20040201202313.GA20053@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.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