From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29211 invoked by alias); 19 Sep 2003 22:29:12 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 29202 invoked from network); 19 Sep 2003 22:29:12 -0000 Received: from unknown (HELO concert.shout.net) (204.253.184.25) by sources.redhat.com with SMTP; 19 Sep 2003 22:29:12 -0000 Received: from duracef.shout.net (duracef.shout.net [204.253.184.12]) by concert.shout.net (8.12.10/8.12.10) with ESMTP id h8JMTAHt002502; Fri, 19 Sep 2003 17:29:10 -0500 Received: from duracef.shout.net (localhost [127.0.0.1]) by duracef.shout.net (8.12.10/8.12.9) with ESMTP id h8JMTAVd021833; Fri, 19 Sep 2003 17:29:10 -0500 Received: (from mec@localhost) by duracef.shout.net (8.12.10/8.12.9/Submit) id h8JMT9q0021832; Fri, 19 Sep 2003 18:29:09 -0400 Date: Fri, 19 Sep 2003 22:29:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200309192229.h8JMT9q0021832@duracef.shout.net> To: jimb@redhat.com Subject: Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3 Cc: gdb@sources.redhat.com X-SW-Source: 2003-09/txt/msg00249.txt.bz2 I think it's good to send the patch to gdb-patches as usual, and then mail to gdb-gnats with a URL that points to the patch. That means you have to for the patch to show up in the gdb-patches archive, but that takes just a few seconds. Michael C