Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: muller@ics.u-strasbg.fr, brobecker@adacore.com,
	gdb-patches@sourceware.org,         gdb@sourceware.org
Subject: Re: [RFC] GDB ARIndex Linux rule cleanup
Date: Wed, 15 Apr 2009 18:55:00 -0000	[thread overview]
Message-ID: <200904151855.n3FIt3m2011311@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <83r5ztlrj9.fsf@gnu.org> from "Eli Zaretskii" at Apr 15, 2009 09:07:22 PM

Eli Zaretskii wrote:
> > Date: Wed, 15 Apr 2009 19:34:08 +0200 (CEST)
> > From: "Ulrich Weigand" <uweigand@de.ibm.com>
> > Cc: muller@ics.u-strasbg.fr, brobecker@adacore.com, gdb-patches@sourceware.org,
> >         gdb@sourceware.org
> > 
> > Yes, the ppc-linux-tdep.c file, which defines the gdbarch struct to be used
> > when debugging an application built for GNU/Linux on the PowerPC platform,
> > in either native, remote, or core file debugging mode.
> > 
> > In fact, in this specific file, some elements of the gdbarch struct are
> > clearly kernel-related (e.g. the ppc_linux_write_pc method to properly
> > restart interrupted system calls, or the signal trampoline unwinders), some
> > elements have nothing whatsoever to do with the kernel (e.g. the
> > ppc_linux_memory_remove_breakpoint method that deals with the fact that
> > ld.so on powerpc modifies code, or the ppc64_skip_trampoline_code method
> > which recognizes linker-generated stubs, or the
> > ppc64_linux_convert_from_func_ptr_addr method that interprets the function
> > pointer ABI), and some could be considered either way (e.g. the core file
> > register set definitions -- a core file may be generated by the kernel,
> > but also other tools, including GDB itself).
> 
> The point is that the elements that are unrelated to the Linux kernel
> are also unrelated to GNU.

I was replying to your statement that 

  I think GDB's "target" is always the OS kernel, not the OS itself.

with the point that all those elements are related to, and in fact defined
by, the *target operating system*; the OS defines the ABI applications
need to use, and in the GNU/Linux case, even provides the toolchain and
system libraries that implement those elements.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


      reply	other threads:[~2009-04-15 18:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 15:29 GDB ARIndex cleanup Pierre Muller
2009-03-26 20:53 ` Eli Zaretskii
2009-03-27  8:23   ` Pierre Muller
2009-03-27  8:47     ` Eli Zaretskii
2009-03-27 14:12       ` Eli Zaretskii
2009-03-27 15:35         ` Eli Zaretskii
2009-04-02 15:12         ` Thiago Jung Bauermann
2009-04-02 19:40           ` Eli Zaretskii
2009-04-02 20:34             ` Joel Brobecker
2009-03-26 23:18 ` Joel Brobecker
2009-03-27  2:22   ` Daniel Jacobowitz
2009-03-27  8:43   ` Pierre Muller
2009-03-27 16:04     ` Joel Brobecker
2009-03-27 16:46       ` Daniel Jacobowitz
2009-04-14 23:06   ` [RFC] GDB ARIndex Linux rule cleanup Pierre Muller
2009-04-14 23:23     ` Mark Kettenis
2009-04-14 23:38       ` Pedro Alves
2009-04-14 23:41         ` Joel Brobecker
2009-04-15  7:06           ` Pierre Muller
2009-04-15  7:33           ` Eli Zaretskii
2009-04-15 14:00     ` Ulrich Weigand
2009-04-15 14:21       ` Pedro Alves
2009-04-15 15:32         ` Ulrich Weigand
2009-04-15 15:54           ` Pedro Alves
2009-04-15 14:25       ` Eli Zaretskii
2009-04-15 15:15         ` Daniel Jacobowitz
2009-04-15 15:23         ` Ulrich Weigand
2009-04-15 15:34           ` Mark Kettenis
2009-04-15 16:00             ` Eli Zaretskii
2009-04-15 16:04           ` Eli Zaretskii
2009-04-15 17:34             ` Ulrich Weigand
2009-04-15 18:07               ` Eli Zaretskii
2009-04-15 18:55                 ` Ulrich Weigand [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=200904151855.n3FIt3m2011311@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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