From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [COMMIT PATCH 2/2] Move savestring to common/common-utils.c, make gdbserver use it.
Date: Thu, 14 Feb 2013 21:05:00 -0000 [thread overview]
Message-ID: <20130214210451.GA4550@adacore.com> (raw)
In-Reply-To: <877gmaiqg5.fsf@fleche.redhat.com>
> Joel> Lynx178 might also be an issue. Agreed on all other counts.
> Joel> I was hoping that gnulib would be our saviour, but maybe it does not
> Joel> implement everything we need (yet?).
>
> It has xstrndup, though it seems a bit weird to pull in 2 different
> definitions of that function. Also, gnulib updates seem tricky right
> now due to the libiconv situation.
Yeah, I was definitely thinking more long term... If the libiconv
situation is the only thing preventing us from doing an update,
I'd go ahead, because the only known platform where this is known
to potentially cause trouble is Lynx178, which I am going to guess
is a fairly little used system. And AFAICT, working around the issue
should be easily done by adding -DE...=... in CFLAGS when configuring
the debugger.
--
Joel
next prev parent reply other threads:[~2013-02-14 21:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 17:14 [COMMIT PATCH 1/2] savestring: Rename parameter 'size' to 'len' Pedro Alves
2013-02-14 17:14 ` [COMMIT PATCH 2/2] Move savestring to common/common-utils.c, make gdbserver use it Pedro Alves
2013-02-14 18:07 ` Tom Tromey
2013-02-14 18:08 ` Pedro Alves
2013-02-14 18:10 ` Tom Tromey
2013-02-14 18:14 ` Pedro Alves
2013-02-14 18:24 ` Tom Tromey
2013-02-14 18:31 ` Pedro Alves
2013-02-14 18:54 ` Joel Brobecker
2013-02-14 20:35 ` Tom Tromey
2013-02-14 21:05 ` Joel Brobecker [this message]
2013-02-21 21:15 ` Tom Tromey
2013-02-14 18:30 ` [COMMIT PATCH 1/2] savestring: Rename parameter 'size' to 'len' Mark Kettenis
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=20130214210451.GA4550@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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