Re: Problem building 2.0 On Ubuntu Maverick

[Billy O'Connor]

Andy Wingo <address@hidden> writes:

> Hi Billy,
>
> On Wed 16 Feb 2011 19:06, Billy O'Connor <address@hidden> writes:
>
>>   GEN    guile-procedures.texi
>> Throw without catch before boot:
>>
>> Error while printing exception:
>> Key: 
>> Failed to print exception.
>> Aborting.
>
> Can you run meta/gdb-uninstalled-guile -q --no-auto-compile ?
>
> That will drop you into a GDB prompt.  You type "run", then when it
> aborts, "backtrace" and send us the report.

Thanks, that solved it.  ;)

When I changed my CFLAGS to "-g -O2" for the backtrace, the error went
away.  
My usual CFLAGS are "-Os -march=native -fomit-frame-pointer -pipe"

I consider this matter resolved, but here's the original backtrace
without the debug info:

pReading symbols from /home/billyoc/guile-2.0.0/libguile/.libs/lt-guile...(no 
debugging symbols found)...done.
(gdb) run
Starting program: /home/billyoc/guile-2.0.0/libguile/.libs/lt-guile -q 
--no-auto-compile
[Thread debugging using libthread_db enabled]
Throw without catch before boot:

Error while printing exception:
Key: 
Failed to print exception.
Aborting.

Program received signal SIGABRT, Aborted.
0x0012e416 in __kernel_vsyscall ()
(gdb) bt
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x004a7941 in raise () from /lib/libc.so.6
#2  0x004aae42 in abort () from /lib/libc.so.6
#3  0x001d3952 in pre_init_throw ()
   from /home/billyoc/guile-2.0.0/libguile/.libs/libguile-2.0.so.22
#4  0x001d9e50 in vm_regular_engine ()
   from /home/billyoc/guile-2.0.0/libguile/.libs/libguile-2.0.so.22
#5  0x00000000 in ?? ()