From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb@sourceware.org
Subject: Re: GDB transition to GPLv3 should now be complete
Date: Fri, 24 Aug 2007 16:16:00 -0000 [thread overview]
Message-ID: <200708241616.l7OGGOhD010090@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070824153333.GA30256@caradoc.them.org> (message from Daniel Jacobowitz on Fri, 24 Aug 2007 11:33:33 -0400)
> Date: Fri, 24 Aug 2007 11:33:33 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Fri, Aug 24, 2007 at 05:28:42PM +0200, Mark Kettenis wrote:
> > > Date: Fri, 24 Aug 2007 11:12:51 -0400
> > > From: Joel Brobecker <brobecker@adacore.com>
> > >
> > > GDB is now licensed under the terms of GPLv3.
> > >
> > > There is one issue identified left before the release: printing of
> > > signed and unsigned characters and strings. I found the patch
> > > submission, but it looks like it never went in (for lack of agreement
> > > on it?).
> >
> > Yes, and I think the only reasonable thing to do in this case is to
> > stick with historical behaviour.
>
> I posted a patch for what I believe is a better reasonable choice, on
> July 5th. If you don't think it is acceptable, could you respond to
> it, please?
>
> http://sourceware.org/ml/gdb-patches/2007-07/msg00101.html
I thought I did. Anyway, the arguments have been given before:
1. There is quite a bit of code that uses "unsigned char *" for
strings, to avoid unwanted sign extension.
2. Not all debug formats (most notably stabs) do not make the
distinction between unqualified "char" and "(un)signed char".
Mark
next prev parent reply other threads:[~2007-08-24 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 15:08 Joel Brobecker
2007-08-24 15:28 ` Mark Kettenis
2007-08-24 15:33 ` Daniel Jacobowitz
2007-08-24 16:16 ` Mark Kettenis [this message]
2007-08-24 16:54 ` Daniel Jacobowitz
2007-08-24 18:11 ` Mark Kettenis
2007-08-24 18:40 ` Daniel Jacobowitz
2007-08-24 22:17 ` Daniel Jacobowitz
2007-08-25 9:36 ` Eli Zaretskii
2007-08-25 13:39 ` Daniel Jacobowitz
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=200708241616.l7OGGOhD010090@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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