Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix OpenBSD/i386 and OpenBSD/amd64 kernel trapframe unwinders
Date: Thu, 22 Dec 2005 19:45:00 -0000	[thread overview]
Message-ID: <20051222142013.GA3110@nevyn.them.org> (raw)
In-Reply-To: <200512221409.jBME9L7W005129@elgar.sibelius.xs4all.nl>

On Thu, Dec 22, 2005 at 03:09:21PM +0100, Mark Kettenis wrote:
> +
> +  find_pc_partial_function (func, &name, NULL, NULL);
> +  if (name && strncmp(name, "Xintr", 5) == 0)
> +    addr = sp + 8;		/* It's an interrupt frame.  */
> +  else
> +    addr = sp;
> +

Is this series of patches really a good idea?

I realize there's no way to configure GDB at runtime to do this sort of
thing, and I accept that that's a serious shortcoming that we
eventually need to fix.  But you're adding bits to the OpenBSD target
that only make sense in terms of the naming conventions of a single
OpenBSD program (which happens to be the kernel); I've resisted doing
this in the past both for The Server Then Known As XFree86 and for the
Linux kernel.  Why should GDB know the names of functions in a single
one of the infinitely many things it might be debugging?

On a less metaphysical note, I'd worry about any other program with a
function named Xintr.

On a nitpicking note, you missed a space before a parenthesis above :-)

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-12-22 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22 17:07 Mark Kettenis
2005-12-22 19:45 ` Daniel Jacobowitz [this message]
2005-12-22 22:46   ` Mark Kettenis
2005-12-23  8:29     ` Daniel Jacobowitz
2005-12-23 14:29       ` Mark Kettenis
2005-12-23 18:46         ` 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=20051222142013.GA3110@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --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