From: Carlo Wood <carlo@alinoe.com>
To: gdb@sources.redhat.com
Subject: Re: Is this information correct?
Date: Mon, 27 May 2002 21:30:00 -0000 [thread overview]
Message-ID: <20020528063001.A16230@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.
Blah, its 6:30 am now... but we figured out what it was.
It was not gdb's fault, nor gcc's fault. The "problem"
was that he was using -O2 and setting a break point
for main causes the break point to be set 4 bytes behond
'main' (the function pointer) which was already at the
start of some inlined constructor for which is was not
clear that it would be there (-O2 magic etc).
Anyway, my (independantly from gdb written) libcwd gave
exactly the same source file line number info ;).
I'll remove the remark that gdb-5.2 might not work with
g++ 3.1. It works.
--
Carlo Wood <carlo@alinoe.com>
next prev parent reply other threads:[~2002-05-28 4:30 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
2002-05-27 21:30 ` Carlo Wood [this message]
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=20020528063001.A16230@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