Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: pedro_alves@portugalmail.pt (Pedro Alves),
	gdb-patches@sourceware.org,
	        brobecker@adacore.com (Joel Brobecker)
Subject: Re: [commit/AIX] Fix error when loading core file
Date: Thu, 31 May 2007 21:24:00 -0000	[thread overview]
Message-ID: <200705312107.l4VL7o1X011554@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070528205203.GA911@localhost.localdomain> from "Daniel Jacobowitz" at May 28, 2007 04:52:03 PM

Daniel Jacobowitz wrote:
> On Mon, May 28, 2007 at 10:00:30PM +0200, Ulrich Weigand wrote:
> > Hmmm, I'm not sure how this would work for core files.  It looks like
> > solib-target would work only for targets that provide
> > to_get_shared_libraries -- are you suggesting to implement that for
> > the core file target?  I guess that would be a gdbarch callback to
> > implement the AIX-specific handling?
> 
> Right - that's exactly what I meant.  Except that I'm thinking now
> that I made a mistake; I could have added a target object instead,
> and then we could use a gdbarch method to implement that target object
> based on a core file.  That's why I haven't followed up on the patch
> yet; I'm going to try re-working it when I get back from vacation.

Sounds good, I think this would indeed work for the AIX case as well.

> As to what the contents of the target object should be, I'm not sure.
> The easiest choice would be the same as the remote protocol format,
> e.g. "Name:HEXSTR,TextSeg=ADDR;Name:HEXSTR,TextSeg=Addr".  The other
> alternative would be XML in case we think any flexibility would be
> needed.  The nice thing about that is it avoids having to hex-encode
> the name; we can XML-escape it instead, which is easier in common
> cases.  Now that we have a nicely simple XML parsing infrastructure I
> like to take advantage of it.

Do we also have infrastructure to *generate* XML?  We have to create
those contents in GDB (at least for the core file and AIX native
target cases).

Bye,
Ulrich

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


  reply	other threads:[~2007-05-31 21:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-20  0:01 Joel Brobecker
2007-05-20 15:12 ` Ulrich Weigand
2007-05-20 15:50   ` Pedro Alves
2007-05-20 23:22     ` Pedro Alves
2007-05-21 13:24       ` Ulrich Weigand
2007-05-21 13:32         ` Daniel Jacobowitz
2007-05-28 20:00           ` Ulrich Weigand
2007-05-28 20:52             ` Daniel Jacobowitz
2007-05-31 21:24               ` Ulrich Weigand [this message]
2007-05-31 21:43                 ` Daniel Jacobowitz
2007-05-22 18:14   ` Joel Brobecker
2007-05-22 23:19     ` Joel Brobecker

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=200705312107.l4VL7o1X011554@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@portugalmail.pt \
    /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