From: "Eli Zaretskii" <eliz@elta.co.il>
To: dvenkat@noida.hcltech.com
Cc: robertso@somerset.sps.mot.com, delzhao_linux@yahoo.com,
"gdb@sources.redhat.com"
<E04CF3F88ACBD5119EFE00508BBB212109262AB8@exch-01.noida.hcltech.com>
(dvenkat@noida.hcltech.com)
Subject: Re: Why GCC/ GDB ignore a normal C statement?
Date: Thu, 08 May 2003 16:07:00 -0000 [thread overview]
Message-ID: <9003-Thu08May2003190252+0300-eliz@elta.co.il> (raw)
> From: "D.Venkatasubramanian, Noida" <dvenkat@noida.hcltech.com>
> Date: Thu, 8 May 2003 10:37:27 +0530
>
> Debugging with all optimizations can result in abnormal jumps, as is
> expected due to instruction scheduling.
I find this not a grave problem, although it does take some time to
become accustomed to. The benefit is that I always test and debug the
same program I'm going to release, and never have to retest due to a
different build.
next reply other threads:[~2003-05-08 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 16:07 Eli Zaretskii [this message]
2003-05-09 10:56 ` Felix Lee
-- 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=9003-Thu08May2003190252+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=E04CF3F88ACBD5119EFE00508BBB212109262AB8@exch-01.noida.hcltech.com \
--cc=delzhao_linux@yahoo.com \
--cc=dvenkat@noida.hcltech.com \
--cc=robertso@somerset.sps.mot.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).