From: Lionel B <lionelb.nospam@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Including <iostream> affects whether or not program freezes?
Date: Wed, 09 Jul 2008 12:03:00 -0000 [thread overview]
Message-ID: <g527ch$oma$1@ger.gmane.org> (raw)
In-Reply-To: <beb51c260807081931u75f058a5wa15c371dba05685d@mail.gmail.com>
On Wed, 09 Jul 2008 03:31:35 +0100, James Gregory wrote:
> 1. Compile with MSVC 7.1, no optimization: my program doesn't freeze 2.
> Compile with MSVC 7.1, with optimization: my program doesn't freeze 3.
> Compile with gcc 4.2.3 (Ubuntu 64 bit), no optimization: my program
> doesn't freeze
> 4. Compile with gcc 4.2.3 (Ubuntu 64 bit), with optimization: my program
> freezes in a particular function 5. Compile with gcc 4.2.3 (Ubuntu 64
> bit), with optimization, and include <iostream> at the top of the file
> where the function which freezes is defined: my program doesn't freeze
You give *way* too little information to even begin to guess what the
problem might be... but this smells like a classic case of Undefined
Behaviour - sometimes it appears to work, sometimes it doesn't. I.e. you
have a bug in your program.
> Debugging this is difficult.
It frequently is ;-) but what other choice do you have? There are tools
to help (debuggers such as gdb, memory leak checkers such as
valgrind, ...)
First I would try stripping your program down to a minimal core that
exhibits the buggy behaviour. Often in doing so you will isolate and
identify the bug. If not seek help here or in a C (or C++, you don't say
which language your program is in) forum. You can post minimal code
demonstrating the problem.
--
Lionel B
next prev parent reply other threads:[~2008-07-09 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 3:26 James Gregory
2008-07-09 12:03 ` Lionel B [this message]
2008-07-09 16:49 ` James Gregory
2008-07-09 18:08 ` Burlen Loring
2008-07-09 13:43 ` Andrew Bell
2008-07-09 14:35 ` Andrew Haley
2008-07-09 17:02 ` Chris Jefferson
2008-07-10 10:58 ` James Gregory
2008-08-05 6:45 ` Christoph Bartoschek
2008-08-05 9:31 ` James Gregory
2008-07-12 21:16 ` James Gregory
2008-07-12 21:05 ` James Gregory
2008-07-12 22:11 ` James Gregory
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='g527ch$oma$1@ger.gmane.org' \
--to=lionelb.nospam@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).