From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Fix linking on non-x86* after libgdb.a removal
Date: Thu, 05 Jan 2012 17:12:00 -0000 [thread overview]
Message-ID: <201201051712.q05HCBu8024844@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20120105152451.GA4548@host2.jankratochvil.net> from "Jan Kratochvil" at Jan 05, 2012 04:24:51 PM
Jan Kratochvil wrote:
> On Thu, 05 Jan 2012 15:46:19 +0100, Ulrich Weigand wrote:
> > Maybe a better way would be to just unconditionally add corelow.o to
> > COMMON_OBS and be done with it? What would be the harm in having the
> > core target always present, even in configurations where no core file
> > formats will be recognized?
>
> Currently GDB writes:
> GDB can't read core files on this machine.
>
> I guess it will load the core file without recognizing its registers?
> I do not have available any core file from the legacy *-tdep.c archs.
> That can be considered a regression.
I guess so. Well, it should be straightforward to add a check to
corelow.c and give the same error message as above if:
- there are no old-style core_fns handlers installed at all, and
- there is no gdbarch handler for this core file type
That ought to fully replicate the current behaviour.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2012-01-05 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 20:43 Jan Kratochvil
2012-01-05 14:46 ` Ulrich Weigand
2012-01-05 15:25 ` Jan Kratochvil
2012-01-05 17:10 ` [commit, s390] Move corelow.o to target config (Re: [patch 2/2] Fix linking on non-x86* after libgdb.a removal) Ulrich Weigand
2012-01-05 17:12 ` Ulrich Weigand [this message]
2012-01-09 21:02 ` [patch 2/2] Fix linking on non-x86* after libgdb.a removal Jan Kratochvil
2012-01-10 16:06 ` Ulrich Weigand
2012-01-10 17:17 ` [commit] " Jan Kratochvil
2012-01-10 19:32 ` Pedro Alves
2012-01-10 19:55 ` Jan Kratochvil
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=201201051712.q05HCBu8024844@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).