This is the mail archive of the
mailing list for the GDB project.
Re: GDB C++ support
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- To: mec at shout dot net
- Cc: gdb at sources dot redhat dot com, sassi at uni dot de
- Date: Tue, 15 Jan 2002 19:11:30 +0200
- Subject: Re: GDB C++ support
- References: <200201151357.HAA17255@duracef.shout.net>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Tue, 15 Jan 2002 07:57:32 -0600
> From: Michael Elizabeth Chastain <email@example.com>
> eli> Do you (or someone else) happen to know whether v5.1 solves some or
> eli> all of the specific problems Guido described in his message? If not,
> eli> he has no reason to try GDB 5.1, does he?
> Well, gdb 5.0 was released more than a year before gcc 3.0, and gdb 5.1
> was released more than 5 months after gcc 3.0. That's a good reason
> to expect that gdb 5.1 will work a lot better than gdb 5.0 when the
> target program is compiled with gcc 3.0.3.
Yes, the principles are well understood.
> I don't have gcc 3.0.3 installed yet (I wish I did). I don't have
> djgpp 2.03 installed (I probably never will). And I don't have time
> to chase after user bug reports with incomplete source code and gdb 5.0.
You don't need to apologize about not having the information I asked
for. But there's no need to be harsh, either. Guido wanted to get
specific help for his specific problem; if no one has the answer, then
the ensuing silence will be self-explanatory ;-)
(Btw, there's nothing DJGPP-specific in what Guido asked: DJGPP
supports both stabs and DWARF2 debugging, so if someone can answer the
questiions for GNU/Linux, say, they will be good for DJGPP as well.)