Ludovic Brenta wrote:
> If you would like to help debug GPS, please start by downloading the
> source package and editing the top-level "gps.gpr" file. Look for
> package Builder, and add "-g" to the Default_Switches ("Ada") line, e.g.
>
> package Builder is
> for Default_Switches ("Ada") use ("-g", ...);
> end Builder;
>
> then do "debian/rules gnat-gps". After a long time (3h40 on my old
> laptop but only 48 minutes on an AMD64 buildd) you will end up with a
> large file called gnat-gps, containing debugging information. You can
> run that under gdb or (better) gnatgdb from the package gnat-gdb. The
> latter allows you to break on exceptions ("break exception"), so you can
> see where the Storage_Error is being raised.
I grabbed the 3.1.3-3 source and am building that. With the default
build options (no -g) it builds fine but behaves the same way as
3.1.3-2.
With the -g option added to Default_Switches, I get the following:
gcc-4.1 -c -g -gnatafno -gnatVa -I- -gnatA
/usr/src/Debian/Ada/GPS/3.1.3-3/gnat-gps-3.1.3/gvd/gvd/gvd-canvas.adb
+===========================GNAT BUG
DETECTED==============================+
| 4.1.2 20060928 (prerelease) (Debian 4.1.1-15) (x86_64-pc-linux-gnu) GCC
error:|
| in splice_child_die, at dwarf2out.c:5503
|
| Error detected at histories.ads:191:15
|
| Please submit a bug report; see http://gcc.gnu.org/bugs.html.
|
| Use a subject line meaningful to you and us to track the bug.
|
| Include the entire contents of this bug box in the report.
|
| Include the exact gcc-4.1 or gnatmake command that you entered.
|
| Also include sources listed below in gnatchop format
|
| (concatenated together with no headers between files).
|
+==========================================================================+
Please include these source files with error report
Note that list may not be accurate in some cases,
so please double check that the problem can still
be reproduced with the set of files listed.
with a nice long list of files. :-(
> You may also want to try removing all compiler options; maybe the
> compiler is emitting wrong code or something. In particular, I usually
> compile with -gnato (full range checks, so we could get a
> Constraint_Error) and -gnatVa (full optional run-time checks, which can
> raise various exceptions). If you remove these options, you'll stand a
> lesser chance of getting exceptions and a higher chance of getting
> random memory corruption and segfaults :/
Hmm...I'll experiment a bit with that.
--
Kevin Brown [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
