From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9574 invoked by alias); 11 Sep 2004 15:52:18 -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 9564 invoked from network); 11 Sep 2004 15:52:16 -0000 Received: from unknown (HELO blount.mail.mindspring.net) (207.69.200.226) by sourceware.org with SMTP; 11 Sep 2004 15:52:16 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by blount.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1C6AAa-0007OJ-00; Sat, 11 Sep 2004 11:52:08 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id A4A4A4B102; Sat, 11 Sep 2004 11:52:41 -0400 (EDT) Date: Sat, 11 Sep 2004 15:52:00 -0000 From: Michael Chastain To: monika@acmet.com, gdb@sources.redhat.com Subject: Re: debugger 6.2.1 misfeatures Message-ID: <41431F49.nailCH317KU2M@mindspring.com> References: <004501c497e5$a53cd9b0$5100a8c0@monika> In-Reply-To: <004501c497e5$a53cd9b0$5100a8c0@monika> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg00087.txt.bz2 "Monika Chaddha" wrote: > Is it necessary to send test cases with the bug? Depends on the bug. It's necessary to send enough info for someone else to reproduce the bug. > I had sent the following bug with patch some days ago but didn't get any > response regarding this. I don't have any test case till now to prove > this bug as it can be test only for remote target during tracing. What > should I do? Pls help. First check the file sim/MAINTAINERS and make sure you're sending to the specific maintainer as well as gdb-patches@. Post. Wait a week, then send it again with a note indicating that it's a repost, with the dates of the previous post. Wait another week, do it again (with all the previous dates). Wait another week, do it again. Wait another week, do it again. Wait another week, do it again. After a month of this, start a separate thread asking for an additional maintainer for the area that you're patching. The longest I've had to wait this year has been 125 days. Michael Chastain honor fdny -- give blood