From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16150 invoked by alias); 6 Jan 2004 01:12:23 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 16143 invoked from network); 6 Jan 2004 01:12:22 -0000 Received: from unknown (HELO smtp6.mindspring.com) (207.69.200.110) by sources.redhat.com with SMTP; 6 Jan 2004 01:12:22 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 1Adflc-0005wR-00; Mon, 05 Jan 2004 20:12:20 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 131C44B35A; Mon, 5 Jan 2004 20:12:38 -0500 (EST) To: cagney@gnu.org, nick@nick.uklinux.net Subject: Re: [PATCH: gdb/mi] -stack-list-locals testcase Cc: gdb-patches@sources.redhat.com Message-Id: <20040106011238.131C44B35A@berman.michael-chastain.com> Date: Tue, 06 Jan 2004 01:12:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-01/txt/msg00127.txt.bz2 Line number differences say that gdb stopped on a different line. Sometimes this is legal gdb behavior, and sometimes it indicates a problem in gdb or in the debug output of gcc or in the interface between the two. Someone has to look closely at the gdb.log and decide which line number(s) are legal to stop on. If gdb stops on a different line number than it's supposed to, that is a bug, and it gets a FAIL or a KFAIL or an XFAIL. Michael C