From: "Eli Zaretskii" <eliz@gnu.org>
To: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>
Cc: gdb@sources.redhat.com
Subject: Re: bug disappears if compiled with -O0
Date: Mon, 26 Jul 2004 05:47:00 -0000 [thread overview]
Message-ID: <2914-Mon26Jul2004065339+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040725223832.GB8947@ata.cs.hun.edu.tr> (message from Baurjan Ismagulov on Mon, 26 Jul 2004 00:38:33 +0200)
> Date: Mon, 26 Jul 2004 00:38:33 +0200
> From: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>
>
> I'm trying to track down a problem in a dynamic library. However, the
> bug doesn't show up if the code is compiled with -O0 (it is normally
> compiled with -O2). Any pointers or tips on how to proceed (except
> printf)?
Just debug as usual, GDB can debug optimized code.
In fact, I suggest to do that always, since if you debug a program
compiled without optimizations, then ship a binary compiled with -O2,
you in effect debugged and tested a similar, but quite different code.
prev parent reply other threads:[~2004-07-26 3:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 3:10 Baurjan Ismagulov
2004-07-26 3:55 ` Michael Chastain
2004-07-26 21:13 ` Baurjan Ismagulov
2004-07-26 21:19 ` Kip Macy
2004-07-27 0:52 ` Michael Chastain
2004-07-26 5:47 ` Eli Zaretskii [this message]
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=2914-Mon26Jul2004065339+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ibr@ata.cs.hun.edu.tr \
/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