From: Danny Backx <danny.backx@scarlet.be>
To: tromey@redhat.com
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: Build question
Date: Fri, 11 Sep 2009 14:41:00 -0000 [thread overview]
Message-ID: <1252680173.8804.25.camel@pavilion> (raw)
In-Reply-To: <m3skevq4b7.fsf@fleche.redhat.com>
On Wed, 2009-09-09 at 13:57 -0600, Tom Tromey wrote:
> >>>>> "Danny" == Danny Backx <danny.backx@scarlet.be> writes:
> Danny> Index: bfd/archive.c
> Changes to BFD need approval from the binutils maintainers.
>
> Do you need most of these changes? I thought perhaps you would only
> need a change in the one place where the DLL name is searched for on the
> host filesystem.
>
> Danny> Index: gdb/top.c
> Danny> +/* Filesystem type */
> Danny> +int have_dos_based_file_system = 0;
>
> Danny> Index: include/filenames.h
>
> include is part of libiberty, so you'll need approval from the libiberty
> maintainers.
>
> Given that more programs than gdb use BFD and libiberty, you will at the
> very least need to put have_dos_based_file_system elsewhere (i.e., in
> libiberty).
I'll create a version 3 of my patch (stripped down) and ask binutils and
libiberty owners.
I'll look into the other issue too (whether it would be possible to do
the right thing when setting the variable in the middle of a session).
Question : it looks like breaking a gdb-gdbserver session always kills
the inferior. Or at least it does so on my target. Has this been subject
of research yet ? I would expect it to be possible to detach without
killing the inferior, much like you can when debugging a linux process
from a linux gdb.
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
next prev parent reply other threads:[~2009-09-11 14:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1250803105.11282.96.camel@pavilion>
[not found] ` <m3fxbl2jib.fsf@fleche.redhat.com>
[not found] ` <83d46pgjkq.fsf@gnu.org>
[not found] ` <1250877901.11282.116.camel@pavilion>
[not found] ` <83ab1tgh9h.fsf@gnu.org>
[not found] ` <1250880746.11282.128.camel@pavilion>
[not found] ` <m3r5v425lu.fsf@fleche.redhat.com>
[not found] ` <1250931899.11282.142.camel@pavilion>
[not found] ` <83skfkfa4n.fsf@gnu.org>
[not found] ` <1251095160.16357.352.camel@pavilion>
[not found] ` <1251828295.6106.119.camel@pavilion>
[not found] ` <83zl9e8nro.fsf@gnu.org>
[not found] ` <1251835928.6106.124.camel@pavilion>
[not found] ` <83vdk281xb.fsf@gnu.org>
[not found] ` <1252143311.6106.252.camel@pavilion>
2009-09-05 16:12 ` Eli Zaretskii
2009-09-07 22:12 ` Joel Brobecker
2009-09-08 15:53 ` Danny Backx
2009-09-08 20:13 ` Danny Backx
2009-09-09 19:57 ` Tom Tromey
2009-09-11 14:41 ` Danny Backx [this message]
2009-09-11 15:22 ` Pedro Alves
2009-09-11 15:28 ` Pedro Alves
2009-09-12 14:48 ` Danny Backx
2009-09-12 15:03 ` Pedro Alves
2009-09-12 16:58 ` Danny Backx
2009-09-13 16:10 ` Pedro Alves
2009-09-13 18:07 ` Danny Backx
2009-09-12 14:53 ` Danny Backx
2009-09-13 9:30 ` Danny Backx
2009-09-13 16:04 ` Joel Brobecker
2009-09-14 18:03 ` Tom Tromey
2009-09-14 18:25 ` Pedro Alves
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=1252680173.8804.25.camel@pavilion \
--to=danny.backx@scarlet.be \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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