From: Joern Rennecke <amylaar@cambridge.redhat.com>
To: dan@cgsoftware.com (Daniel Berlin)
Cc: amylaar@cambridge.redhat.com (Joern Rennecke),
dan@cgsoftware.com (Daniel Berlin),
mark@codesourcery.com (Mark Mitchell),
wilson@cygnus.com, gcc@gcc.gnu.org
Subject: Re: debugging optimized programs (Was: Re: Bootstrap failure of gcc-ss-20010409 in ia64)
Date: Wed, 18 Apr 2001 15:49:00 -0000 [thread overview]
Message-ID: <200104182249.f3IMnBD07197@phal.cambridge.redhat.com> (raw)
In-Reply-To: <m2wv8hg8n6.fsf@dynamic-addr-83-177.resnet.rochester.edu>
> In the case of heavily intermingled code, the line number info may
> look like (i've omitted is_stmt, basic_block, and other registers, for
> simplicity):
>
> Line advance Address advance
> 0 1
> -1 1
> 2 1
> -1 1
> etc
So that's the way gdb handles it right now. Which can mean that
optimized code is so tedious to debug for some applications and targets
that you try to avoid it at all costs. Not what I'd call 'not being able
to tell the difference'.
next prev parent reply other threads:[~2001-04-18 15:49 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 6:56 Bootstrap failure of gcc-ss-20010409 in ia64 Andreas Schwab
2001-04-11 12:47 ` Jim Wilson
2001-04-11 17:31 ` Mark Mitchell
2001-04-11 17:43 ` Mark Mitchell
2001-04-11 18:28 ` Daniel Berlin
2001-04-11 18:34 ` Mark Mitchell
2001-04-11 20:24 ` Daniel Berlin
2001-04-11 21:19 ` Mark Mitchell
2001-04-11 21:36 ` Daniel Berlin
2001-04-12 12:27 ` Bill Nottingham
2001-04-12 15:03 ` Daniel Berlin
2001-04-12 21:07 ` Bill Nottingham
2001-04-12 21:46 ` Daniel Berlin
2001-04-12 13:04 ` Jim Wilson
2001-04-12 15:06 ` Daniel Berlin
2001-04-13 8:49 ` Andreas Schwab
2001-04-13 10:04 ` Daniel Berlin
2001-04-13 10:23 ` Andreas Schwab
2001-04-13 12:20 ` Daniel Berlin
2001-04-13 12:39 ` Andreas Schwab
2001-04-13 12:56 ` Daniel Berlin
2001-04-13 13:06 ` Andreas Schwab
2001-04-13 19:13 ` Jim Wilson
2001-04-13 19:59 ` Jim Wilson
2001-04-14 2:01 ` Jim Wilson
2001-04-14 4:08 ` Sam TH
2001-04-14 8:27 ` cvs (was: Bootstrap failure of gcc-ss-20010409 in ia64) Fergus Henderson
2001-04-14 11:28 ` Sam TH
2001-04-14 22:20 ` Jim Wilson
2001-04-14 23:48 ` Russ Allbery
2001-04-16 15:39 ` Bootstrap failure of gcc-ss-20010409 in ia64 Jim Wilson
2001-04-16 17:22 ` Mark Mitchell
2001-04-16 17:45 ` Jim Wilson
2001-04-17 8:22 ` Mark Mitchell
2001-04-17 8:57 ` Daniel Berlin
2001-04-17 11:01 ` Jim Wilson
2001-04-17 15:38 ` Mark Mitchell
2001-04-17 16:16 ` Daniel Berlin
2001-04-17 16:36 ` Mark Mitchell
2001-04-18 14:35 ` debugging optimized programs (Was: Re: Bootstrap failure of gcc-ss-20010409 in ia64) Joern Rennecke
2001-04-18 15:12 ` Daniel Berlin
2001-04-18 15:49 ` Joern Rennecke [this message]
2001-04-18 17:06 ` Daniel Berlin
2001-04-18 17:18 ` Daniel Berlin
2001-04-18 12:41 ` Bootstrap failure of gcc-ss-20010409 in ia64 Jim Wilson
2001-04-18 13:49 ` Mark Mitchell
2001-04-18 14:34 ` Jim Wilson
2001-04-18 15:31 ` Mark Mitchell
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=200104182249.f3IMnBD07197@phal.cambridge.redhat.com \
--to=amylaar@cambridge.redhat.com \
--cc=dan@cgsoftware.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=wilson@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).