From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24453 invoked by alias); 3 Oct 2011 16:25:58 -0000 Received: (qmail 24438 invoked by uid 22791); 3 Oct 2011 16:25:56 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 03 Oct 2011 16:25:40 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id C133D2BAFA3; Mon, 3 Oct 2011 12:25:39 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ab+ko+BP6B4W; Mon, 3 Oct 2011 12:25:39 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 92BCC2BAF2A; Mon, 3 Oct 2011 12:25:39 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 67B2A145615; Mon, 3 Oct 2011 12:25:35 -0400 (EDT) Date: Mon, 03 Oct 2011 16:25:00 -0000 From: Joel Brobecker To: Joost van der Sluis Cc: gdb@sourceware.org Subject: Re: Crash of Archer's gdb on mingw (passing null argument to vasprintf) Message-ID: <20111003162535.GL27340@adacore.com> References: <1317634777.28003.15.camel@feddie.cnoc.lan> <20111003145904.GK27340@adacore.com> <1317658598.28003.48.camel@feddie.cnoc.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1317658598.28003.48.camel@feddie.cnoc.lan> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-10/txt/msg00007.txt.bz2 > 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