Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Fix linking on non-x86* after libgdb.a removal
Date: Thu, 05 Jan 2012 15:25:00 -0000	[thread overview]
Message-ID: <20120105152451.GA4548@host2.jankratochvil.net> (raw)
In-Reply-To: <201201051446.q05EkJVV016755@d06av02.portsmouth.uk.ibm.com>

On Thu, 05 Jan 2012 15:46:19 +0100, Ulrich Weigand wrote:
> Jan Kratochvil wrote:
> > For targets using new set_gdbarch_regset_from_core_section it would not be
> > a problem, just put corelow.o into the right entry of gdb/configure.tgt.
> 
> Huh, at least for s390 this would certainly be the correct solution; the
> target actually is fully switched to modern gdbarch core handling ...

I agree and I forgot to write that at least some - at least s390 - targets
properly work with core files on cross-gdb.  But still some other targets do
not.  I find such fix(es) outside of the scope of this proposed patch.
As I found for example on sparc*-tdep.c files it is not so obvious which are
and which are not already converted.


> This needs to be done anyway to properly handle cross-debugging targeting
> s390 core files.  Unless you already have done so, I can prepare a patch.

Sure such (separate) patch would be great.


> 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.


> Or, if we want to keep the existing behaviour exactly, we could just
> filter out all objects from TARGET_OBS that are already present in
> NATDEPFILES (or vice versa).  This would at least avoid the ad-hoc
> handling of one specific file ...

I think one cannot do such filtering in a cross-platform way from Makefile.
But I agree it can be done from configure.ac.  I can rework it that way.

There needs to be some exception for ALL_TARGET_OBS which are not known to
configure.ac, I considered this as a blocker but I see it is not.


Thanks,
Jan


  reply	other threads:[~2012-01-05 15:25 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 [this message]
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     ` [patch 2/2] Fix linking on non-x86* after libgdb.a removal Ulrich Weigand
2012-01-09 21:02       ` 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=20120105152451.GA4548@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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