Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: mludvig@suse.cz
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Re: Analyzing AMD64 corefiles on i386
Date: Wed, 09 Jul 2003 13:38:00 -0000	[thread overview]
Message-ID: <200307091338.h69Dc8u7023807@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3F0BF66A.3080203@suse.cz> (message from Michal Ludvig on Wed, 09 Jul 2003 13:03:06 +0200)

   Date: Wed, 09 Jul 2003 13:03:06 +0200
   From: Michal Ludvig <mludvig@suse.cz>

   This is a multi-part message in MIME format.
   --------------050406070409000508090803
   Content-Type: text/plain; charset=us-ascii; format=flowed
   Content-Transfer-Encoding: 7bit

   Mark Kettenis told me that:
   >    Date: Tue, 08 Jul 2003 14:43:49 +0200
   >    From: Michal Ludvig <mludvig@suse.cz>
   > 
   >    Hi,
   >    what must be done to enable reading of AMD64 corefiles in a gdb running 
   >    on i386 with --target=amd64?
   > 
   > The necessary support for corefiles needs to be added to
   > x86-64-linux-tdep.c.  Take a look at i386nbsd-tdep.c for an example.
   > You'll need to create a `struct core_fns' together with the necessary
   > support functions, and register it with add_core_fns.  Note that for
   > the support functions you can't rely on definitions in header files
   > and such since this is target code.  You'll also need to drop
   > core-regset.o from NATDEPFILES in x86-64-linux.mh.

   How about the attached one? Works for me on cross-gdb i386->amd64 as 
   well as in native amd64 gdb. Can I apply it?

Not as such.  We can't allow public functions with the names
supply_gregset and fill_gregset in *-tdep.c files.  Therefore these
functions should be renamed, and supply_gregset and fill_gregset
should be kept in your *-nat.c file.  You'll probably want to rewrite
those functions such that they call the new functions in *-tdep.c.

Personally I wouldn't define all those constants if the only place
where they'll be used is the regmap array, but that's a matter of
taste.

Mark


  parent reply	other threads:[~2003-07-09 13:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3F0ABC85.1080700@suse.cz>
     [not found] ` <200307081445.h68EjBWJ000503@elgar.kettenis.dyndns.org>
2003-07-09 11:03   ` Michal Ludvig
2003-07-09 11:56     ` Andreas Schwab
2003-07-09 13:40       ` Mark Kettenis
2003-07-09 13:38     ` Mark Kettenis [this message]
2003-07-09 18:08       ` Daniel Jacobowitz
2003-07-09 19:52         ` Andrew Cagney
2003-07-09 21:46         ` Mark Kettenis
2003-07-10 10:05       ` Michal Ludvig
2003-07-14 19:26         ` Mark Kettenis
2003-07-15 11:34           ` Michal Ludvig

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=200307091338.h69Dc8u7023807@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mludvig@suse.cz \
    /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