From: "James Gregory" <james.jrg@gmail.com>
To: "Chris Jefferson" <chris@bubblescope.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Including <iostream> affects whether or not program freezes?
Date: Thu, 10 Jul 2008 10:58:00 -0000 [thread overview]
Message-ID: <beb51c260807100354n34ab20f8p1214fb31f54b2e97@mail.gmail.com> (raw)
In-Reply-To: <5cc6b04e0807090949g30d5aacckc170e6068093e5a4@mail.gmail.com>
On Wed, Jul 9, 2008 at 5:49 PM, Chris Jefferson <chris@bubblescope.net> wrote:
>> 4. Compile with gcc 4.2.3 (Ubuntu 64 bit), with optimization: my
>> program freezes in a particular function
>>
>> Debugging this is difficult.
>
> While I could well be repeating what others say, my usual tools for
> situations like this, which (touch wood) tend to get me out of it:
>
> A) Turn on all warnings, and read what they say. I've found this kind
> of thing can be caused by a missing return statement.
No warnings...
> B) Turn on the debugging standard library, if you are using any of the
> STL in your code.
OK this reported a problem somewhere else, but fixing it didn't make
any difference to the freezing problem.
> C) Find the minimial set of optimisation flags you need to trigger
> your problem (in particular if you can turn off inlining it will make
> things easier). This makes the next stage easier.
At first it required -finline-functions, but then I manually inlined
an a function called in the part which freezes and now the minimum set
of flags that triggers the problem is:
-O1 -fstrict-aliasing
> D) Use valgrind and see what it comes up with.
Nothing at all.
A minimal version of the function which freezes is something like:
bool AIInterpreter::is_group_like_this(int n_side, int n_group) {
//it is the second condition (scanned_groups) which triggers this
code branch, but deleting anything at all here removes the bug
if ((!sides[n_side].groups[n_group].get_alive())
|| !sides[my_side].scanned_groups[n_side][n_group]
|| sides[n_side].groups[n_group].get_in_hangar()) {
while (l_iter != l_end)
++l_iter;
return false;
}
write_log(L"it never gets this far");
<the function continues but though deleting it removes the bug, the
fact the above log never gets written means it is probably irrelevant>
}
So I guess "while (l_iter != l_end)" is becoming an infinite loop, but
if I log the value of &(*l_iter) and &(*l_end) on each loop then a) it
removes the bug and b) there is nothing obviously wrong. Anything else
I can do?
James
next prev parent reply other threads:[~2008-07-10 10:55 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
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 [this message]
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=beb51c260807100354n34ab20f8p1214fb31f54b2e97@mail.gmail.com \
--to=james.jrg@gmail.com \
--cc=chris@bubblescope.net \
--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).