From: Joost van der Sluis <joost@cnoc.nl>
To: gdb@sourceware.org
Subject: Re: Crash of Archer's gdb on mingw (passing null argument to vasprintf)
Date: Wed, 12 Oct 2011 07:30:00 -0000 [thread overview]
Message-ID: <1318404606.25241.3.camel@feddie.cnoc.lan> (raw)
In-Reply-To: <20111003162535.GL27340@adacore.com>
On Mon, 2011-10-03 at 09:25 -0700, Joel Brobecker wrote:
> > I've found the TYPE_ERROR_NAME macro.
>
> Heh - I didn't know about this one.
But it seems to be the wrong one? Pierre mailed me that this one should
be used for erroneous types. This is not the case here, it just doesn't
have a name. I'll send another patch to gdb-patches.
> You might also want to start a copyright assignment process if you
> are planning on contributing again. We can take one, or maybe two
> small patches, but beyond that, we almost always require that
> the contributor have an assignment on file.
I do have all those papers in order, for some patches to the vla-branch.
Regards,
Joost van der Sluis
next prev parent reply other threads:[~2011-10-12 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 9:39 Joost van der Sluis
2011-10-03 10:07 ` Mark Kettenis
2011-10-03 14:59 ` Joel Brobecker
2011-10-03 16:17 ` Joost van der Sluis
2011-10-03 16:25 ` Joel Brobecker
2011-10-12 7:30 ` Joost van der Sluis [this message]
2011-10-03 16:35 ` 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=1318404606.25241.3.camel@feddie.cnoc.lan \
--to=joost@cnoc.nl \
--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