Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Implement qXfer:libraries for Linux/gdbserver [Was: Re: [RFC] Make target_read_string faster over high-latency links.]
Date: Mon, 08 Aug 2011 18:36:00 -0000	[thread overview]
Message-ID: <20110808183613.GA31998@host1.jankratochvil.net> (raw)
In-Reply-To: <CALoOobM_nZ+Xkv7tqjq-JLOaPSQabOTKnXx29HADOtfQk_Jgrg@mail.gmail.com>

On Fri, 05 Aug 2011 20:10:09 +0200, Paul Pluzhnikov wrote:
> Moving solib-svr4.c to gdb/common doesn't appear necessary: the parts
> that I would have used in gdbserver/linux-low.c are quite small, and not
> easily re-usable.

GDB could reuse solib-target.c and split solib-svr4.c to the small part
getting the library list - providing it for UNIX *-nat.c files as
TARGET_OBJECT_LIBRARIES - and the other UNIX code useful in both local and
remote cases there.  

It would make libexpat mandatory even for the linux-nat.c usage so libexpat
could be bundler into the sourceware tree.

The same way all_dlls->dll_info could be renamed and reused on the server side
even for UNIX, that would be easier.

I do not say it would say LoC but it would be more clean, currently there
would be two isolated producer + consumer pairs of the same protocol.

Sure it may not be so easy as it sounds, I have not tried it.


Thanks,
Jan


  reply	other threads:[~2011-08-08 18:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 18:11 Paul Pluzhnikov
2011-08-08 18:36 ` Jan Kratochvil [this message]
2011-08-08 18:56   ` Paul Pluzhnikov
2011-08-08 21:24     ` [patch] Implement qXfer:libraries for Linux/gdbserver Jan Kratochvil
2011-08-09 18:25       ` Daniel Jacobowitz
2011-08-08 21:10 ` Jan Kratochvil
2011-08-08 21:31   ` Paul Pluzhnikov
2011-08-08 21:38     ` Jan Kratochvil
2011-08-08 23:50       ` Paul Pluzhnikov
2011-08-09  9:07         ` Jan Kratochvil
2011-08-09 16:57           ` Paul Pluzhnikov
2011-08-14 16:36             ` Jan Kratochvil
2011-10-03 21:57               ` IMO-obsolste: " 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=20110808183613.GA31998@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ppluzhnikov@google.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