delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2004/01/13/01:39:53

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: 13 Jan 2004 08:40:07 +0200
Message-Id: <u4qv0gxmg.fsf@elta.co.il>
From: Eli Zaretskii <eliz AT elta DOT co DOT il>
To: djgpp AT delorie DOT com
In-reply-to: <9tbbd1-i32.ln1@phekda.freeserve.co.uk> (message from Richard
Dawe on Mon, 12 Jan 2004 20:16:09 +0000)
Subject: Re: debugging template classes/functions
References: <btuqku$tfn$00$1 AT news DOT t-online DOT com> <9tbbd1-i32 DOT ln1 AT phekda DOT freeserve DOT co DOT uk>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> Date: Mon, 12 Jan 2004 20:16:09 +0000
> From: Richard Dawe <ng AT phekda DOT gotadsl DOT co DOT uk>
> 
> I haven't tried gdb 6 yet - perhaps that has better C++ support than
> 5.x.

C++ debugging support in GDB is being actively worked on, and so
improves significantly with each new version.  Thus, getting the
latest GDB/RHIDE is always a good idea for C++ developers.

However, C++ is a monstrously large and complex language, so there are
currently quite a few known problems with debugging some of its more
complex and arcane features, some of them actually due to GCC
bugs/misfeatures.

If the OP has a specific (preferably short) example of a C++ program
that gives GDB trouble, please post it here so we could try it with
the latest GDB and see if the problems were solved in the meantime.
If they are not solved, they should be brought to the attention of
the GDB developers.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019