From: Michael Veksler <VEKSLER@il.ibm.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB unusable on AIX and lucky to work on HP-UX (PR1170)
Date: Thu, 23 Sep 2004 16:23:00 -0000 [thread overview]
Message-ID: <OFDC1C0F49.80D192F8-ONC2256F18.00591422-C2256F18.005A2484@il.ibm.com> (raw)
In-Reply-To: <20040923154527.GD968@gnat.com>
Joel Brobecker <brobecker@gnat.com> wrote on 2004-09-23 18:45:27:
> Michael,
>
> would have some code that would demonstrate the problem without
> the fiddling? I just looked at the testsuite results on AIX, where
> I use GCC 3.2.3 configured with C,C++ and Ada, and I didn't see any
> such internal-error.
>
There is a real test case in the PR. It generates inputs too big to
understand. If you look at the PR, you can see my analysis that start
with this huge test case, and reduced to simple several lines
that do require fiddling. Unfortunately, /bin/as does not guarantee
order preservation, which makes my fiddling valid:
1. Since future versions of /bin/as may reorder things this way.
2. Any technology that does post link optimization will cause
such problems. I would suspect that FDPR will make the simplest
C code impossible to debug in GDB.
http://www.haifa.il.ibm.com/projects/systems/cot/fdpr/
The test case is as simple as:
$ cat bug.cpp
#include <string>
#include <iostream>
int main() {}
$ g++ -g -fno-inline -fno-default-inline bug.cpp
Note that these flags are critical if you don't want an even bigger
tests case.
prev parent reply other threads:[~2004-09-23 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 10:32 PR1170: wrong assumption on stab = crash Michael Veksler
2004-09-23 10:21 ` GDB unusable on AIX and lucky to work on HP-UX (PR1170) Michael Veksler
2004-09-23 15:45 ` Joel Brobecker
2004-09-23 16:23 ` Michael Veksler [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=OFDC1C0F49.80D192F8-ONC2256F18.00591422-C2256F18.005A2484@il.ibm.com \
--to=veksler@il.ibm.com \
--cc=brobecker@gnat.com \
--cc=gdb@sources.redhat.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).