From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 519 invoked by alias); 28 Feb 2002 00:45:17 -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 375 invoked from network); 28 Feb 2002 00:45:10 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 28 Feb 2002 00:45:10 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id g1S0j6E19785; Wed, 27 Feb 2002 18:45:06 -0600 Date: Wed, 27 Feb 2002 16:45:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200202280045.g1S0j6E19785@duracef.shout.net> To: fnf@redhat.com Subject: Re: [RFC] Gdb line table implementation tweak Cc: gdb-patches@sources.redhat.com X-SW-Source: 2002-02/txt/msg00727.txt.bz2 I'm getting similar failures on: [target=native host=i686-pc-linux-gnu%rh-7.2 gdb=HEAD%2002-02-26 gcc=2.95.3 glibc=vendor goption=-g-stabs+] I put up a gdb.log and gdb.sum file on: ftp://ftp.shout.net/pub/users/mec/step-bug/gdb.sum ftp://ftp.shout.net/pub/users/mec/step-bug/gdb.log A good example of the bad behavior is: gdb.base/step-test: large struct by value gdb tries to step into a function but instead it steps somewhere else. For me, the bug is specific to gcc 2.95.3 and stabs debugging format. Michael C