From: Joel Brobecker <brobecker@adacore.com>
To: Joost van der Sluis <joost@cnoc.nl>
Cc: gdb@sourceware.org
Subject: Re: Crash of Archer's gdb on mingw (passing null argument to vasprintf)
Date: Mon, 03 Oct 2011 16:25:00 -0000 [thread overview]
Message-ID: <20111003162535.GL27340@adacore.com> (raw)
In-Reply-To: <1317658598.28003.48.camel@feddie.cnoc.lan>
> I've found the TYPE_ERROR_NAME macro.
Heh - I didn't know about this one.
> Now another question: how do I send a patch for inclusion in gdb? Can
> I send it to this list? Or gdb-patches?
It is preferable that you submit patches upstream if they apply there.
In that case, please send them to gdb-patches. If they only apply
to project Archer, then you should send them to the archer list.
You should review the contents of the gdb/CONTRIBUTE file, which gives
the initial pointers on how to submit a patch. You're not far off
in this case, but you are missing a ChangeLog entry.
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.
--
Joel
next prev parent reply other threads:[~2011-10-03 16:25 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 [this message]
2011-10-12 7:30 ` Joost van der Sluis
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=20111003162535.GL27340@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=joost@cnoc.nl \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).