public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jędrzej Dudkiewicz" <jedrzej.dudkiewicz@gmail.com>
To: Andrew Haley <aph@redhat.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: sigsegv on aix with gcc
Date: Tue, 07 Jun 2011 07:50:00 -0000	[thread overview]
Message-ID: <BANLkTinASyaSHdqwbKasGY_NyK_346FHRA@mail.gmail.com> (raw)
In-Reply-To: <4DECB30B.4050600@redhat.com>

2011/6/6 Andrew Haley <aph@redhat.com>:
> On 06/06/11 11:43, Jędrzej Dudkiewicz wrote:
>
>> Can you give me ANY pointers regarding further steps? Thanks in advance.
>
> You're just going to have to debug it.  Assuming you've done the obvious
> checking compile-time warning messages, it's time to break out the
> debugger.

Well, that's the first thing I did, but I just can't figure out what
is happening - I compiled with -O (as without optimization everything
"works") so source code isn't exactly the same as binary code, and
many variables are inlined, so I can't print their values.
Additionally - program core dumps in libstdc++, in locale's operator=
- that's not really deep, but I'm not completely aware of situation,
which makes things even harder. Also, same code works fine when
compiled on Linux, HPUX, MacOSX and SunOS with different versions of
gcc. Valgrind under Linux and MacOSX says nothing at all - so my guess
is that there's something "odd" about AIX. I was hoping for some
pointers, like "check this" or "link against that" or "define A".
-- 
Jędrzej Dudkiewicz

I really hate this damn machine, I wish that they would sell it.
It never does just what I want, but only what I tell it.

  reply	other threads:[~2011-06-07  4:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 15:16 Jędrzej Dudkiewicz
2011-06-06 17:29 ` Andrew Haley
2011-06-07  7:50   ` Jędrzej Dudkiewicz [this message]
2011-06-07  8:13     ` Jonathan Wakely

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=BANLkTinASyaSHdqwbKasGY_NyK_346FHRA@mail.gmail.com \
    --to=jedrzej.dudkiewicz@gmail.com \
    --cc=aph@redhat.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).