From: Felix Lee <felix.1@canids.net>
To: gdb@sources.redhat.com
Subject: Re: Why GCC/ GDB ignore a normal C statement?
Date: Fri, 09 May 2003 10:56:00 -0000 [thread overview]
Message-ID: <20030509105645.65CB1158ACE@kanga.local> (raw)
In-Reply-To: <9003-Thu08May2003190252+0300-eliz@elta.co.il> on Thu, 08 May 2003 19:02:53 +0300.
Perhaps gdb could be a little more informative about nonlinear
flow? Not everyone is going to be familiar with what goes on
with instruction scheduling. I do know, and it still confuses me
sometimes.
It doesn't have to be anything complicated, just stuff like:
print "(line 11 was optimized away)" if doing "step" goes from
line 10 to line 12, there are no machine instructions for line
11, and line 11 isn't just comments. For expert users, this
could be reduced to printing a "*" in front of line 12. Or
whatever.
I'd also find it helpful if gdb somehow marked source lines that
were attached to nonconsecutive machine instructions.
The idea is to give just a little more information so I don't
have to spend energy guessing so much.
--
next prev parent reply other threads:[~2003-05-09 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 16:07 Eli Zaretskii
2003-05-09 10:56 ` Felix Lee [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 5:16 D.Venkatasubramanian, Noida
2003-05-05 11:32 Huaxia Zhao
2003-05-06 8:56 ` D.Venkatasubramanian, Noida
2003-05-06 12:52 ` Jim Robertson
2003-05-06 17:17 ` Eli Zaretskii
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=20030509105645.65CB1158ACE@kanga.local \
--to=felix.1@canids.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).