From: Carlo Wood <carlo@alinoe.com>
To: gdb@sources.redhat.com
Subject: Re: Is this information correct?
Date: Mon, 27 May 2002 17:09:00 -0000 [thread overview]
Message-ID: <20020528020900.B12154@alinoe.com> (raw)
In-Reply-To: <20020527180721.GC5523@branoic.them.org>; from drow@mvista.com on Mon, May 27, 2002 at 02:07:21PM -0400
On Mon, May 27, 2002 at 02:07:21PM -0400, Daniel Jacobowitz wrote:
> What's this part about though? I think it's really referring to gdb
> 5.1 instead. 5.2 should be fine.
That was because of this chat I had on IRC:
[03:04] <`Kernel`> Run: not really. I had been awaiting 3.1 to remake world, but unfortunately preliminary tests showed that it outputs crap debug info.
[03:05] <Run> I can't believe that.
[03:05] <Run> Actually, it works fine for me.
[03:05] <`Kernel`> well, on the project I tested with, gdb 5.2 can't find some of the source files.
[03:06] <Run> I have no problems, also using gdb 5.2
[03:06] <`Kernel`> it works perfectly if you switch CXX=g++-3.0.4 instead of g++-3.1
[03:06] <Run> Oh wait
[03:06] <`Kernel`> (and it also says that main() is in some .h)
[03:06] <Run> I had to fix libcwd too because they switched from DW_FORM_string to DW_FORM_strp (pointers into a string table) for source files and directory names.
[03:07] <Run> That could be the reason.
[03:07] <`Kernel`> it could be the reason gdb fails?
[03:07] <Run> I am using the lastest cvs version of gdb, and that works.
[03:07] <Run> yes, because it was changed since 3.1, and it WOULD fuck up the source files
[03:08] <`Kernel`> hmm... ok, I'll try that. Altough gdb 5.2 if I am not mistaken was out May 14, one day before gcc 3.1.
I'll ask `Kernel` if moving to the cvs version of gdb
does help him.
--
Carlo Wood <carlo@alinoe.com>
next prev parent reply other threads:[~2002-05-28 0:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 5:20 Carlo Wood
2002-05-27 11:07 ` Daniel Jacobowitz
2002-05-27 17:09 ` Carlo Wood [this message]
2002-05-27 21:30 ` Carlo Wood
2002-05-28 18:05 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020528020900.B12154@alinoe.com \
--to=carlo@alinoe.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox