From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25733 invoked by alias); 15 Jan 2002 17:48:40 -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 25700 invoked from network); 15 Jan 2002 17:48:39 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 15 Jan 2002 17:48:39 -0000 Received: (from mec@localhost) by duracef.shout.net (8.8.7/8.8.7) id LAA16445; Tue, 15 Jan 2002 11:48:34 -0600 Date: Tue, 15 Jan 2002 09:48:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200201151748.LAA16445@duracef.shout.net> To: eliz@is.elta.co.il Subject: Re: GDB C++ support Cc: gdb@sources.redhat.com, sassi@uni.de X-SW-Source: 2002-01/txt/msg00159.txt.bz2 eli> You don't need to apologize about not having the information I asked eli> for. But there's no need to be harsh, either. Yeah, you're right, I got up grouchy this morning. I apologize for that. Co-incidentally, I'm making test runs with stock 5.1 right now. Here's an excerpt from gdb.log: # gdb 5.1, gcc 3.0.2, -gdwarf-2, gdb.c++/method.exp (gdb) break main^M Breakpoint 1 at 0x8048549: file /berman/migchain/source/gdb-5.1/gdb/testsuite/gdb.c++/method.cc, line 66.^M (gdb) run ^M Starting program: /berman/migchain/build/native/gdb-5.1/gdb/testsuite/gdb.c++/method ^M ^M Breakpoint 1, main () at /berman/migchain/source/gdb-5.1/gdb/testsuite/gdb.c++/method.cc:66^M 66 k = 10;^M (gdb) break A::foo^M Breakpoint 2 at 0x80484a6: file /berman/migchain/source/gdb-5.1/gdb/testsuite/gdb.c++/method.cc, line 38.^M (gdb) PASS: gdb.c++/method.exp: set breakpoint on A::foo continue^M Continuing.^M ^M Breakpoint 2, A::foo(int) (this=0xbffff0e0, arg=13) at /berman/migchain/source/gdb-5.1/gdb/testsuite/gdb.c++/method.cc:38^M 38 x += arg;^M (gdb) FAIL: gdb.c++/method.exp: continuing and breaking in A::foo So you can see that 'break A::foo' works and gdb takes the breakpoint. I don't know what that "FAIL" is about (that is a different issue). Constructively, Michael C