I wrote:
> GDB gives better results. When running the program, the program winds
> up getting a SIGSEGV. It looks to me like the storage manager catches
> that and raises its own exception.
Here's the results of a gdb run against the binary:
[EMAIL PROTECTED]:/usr/src/Debian/Ada/GPS/3.1.3-3/gnat-gps-3.1.3$ gdb gnat-gps
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db library
"/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/src/Debian/Ada/GPS/3.1.3-3/gnat-gps-3.1.3/gnat-gps
[Thread debugging using libthread_db enabled]
[New Thread 46951004957008 (LWP 31813)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46951004957008 (LWP 31813)]
0x00002ab3a0150e3c in signal_parse_name (name=0x7ffffff029b8 "Pp$\002",
itype=<value optimized out>, detail_p=0x85a2e4823200002a,
force_quark=-1281144710) at gsignal.c:281
281 gsignal.c: No such file or directory.
in gsignal.c
Current language: auto; currently c
(gdb) where
#0 0x00002ab3a0150e3c in signal_parse_name (name=0x7ffffff029b8 "Pp$\002",
itype=<value optimized out>, detail_p=0x85a2e4823200002a,
force_quark=-1281144710) at gsignal.c:281
#1 0x0000000000000000 in ?? ()
(gdb) cont
Continuing.
raised STORAGE_ERROR : s-intman.adb:158 explicit raise
Program exited with code 01.
(gdb) quit
The SIGSEGV occurred when I tried to open a file.
This doesn't look very useful, especially given that I can't even get
a traceback. :-(
--
Kevin Brown [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
