Problem building 2.0 On Ubuntu Maverick

Problem building 2.0 On Ubuntu Maverick

[Billy O'Connor]

This error seems familiar to me somehow, but I can't place it or find
anything in the ml archives.  Has anyone else seen this?

billyoc@t22:~/guile-2.0.0$ gcc --version
gcc (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5

...

make[3]: Entering directory `/home/billyoc/guile-2.0.0/libguile'
  GEN    guile-procedures.texi
Throw without catch before boot:

Error while printing exception:
Key: 
Failed to print exception.
Aborting.
/bin/bash: line 1: 18691 Broken pipe             cat alist.doc
arbiters.doc arraytevectors.doc chars.doc control.doc continuations.doc
debug.doc deprecated.doc nsions.doc feature.doc fluids.doc foreign.doc
fports.doc gc-malloc.doc gc.doc ge hash.doc hashtab.doc hooks.doc
i18n.doc init.doc ioext.doc keywords.doc list.dodoc pairs.doc ports.doc
print.doc procprop.doc procs.doc promises.doc r6rs-ports.doc sort.doc
srcprop.doc srfi-1.doc srfi-4.doc srfi-13.doc srfi-14.doc
srfi-60.bols.doc threads.doc throw.doc trees.doc uniform.doc values.doc
variable.doc vec.doc regex-posix.doc 
     18692 Aborted                 | GUILE_AUTO_COMPILE=0
     ../meta/uninstalled-en 
make[3]: *** [guile-procedures.texi] Error 1
make[3]: Leaving directory `/home/billyoc/guile-2.0.0/libguile'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/billyoc/guile-2.0.0/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/billyoc/guile-2.0.0'
make: *** [all] Error 2

Re: Problem building 2.0 On Ubuntu Maverick

[Andy Wingo]

Hi Billy,

On Wed 16 Feb 2011 19:06, Billy O'Connor <billyoc@gmail.com> 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!

Andy
-- 
http://wingolog.org/

Re: Problem building 2.0 On Ubuntu Maverick

[Billy O'Connor]

Andy Wingo <wingo@pobox.com> writes:

> Hi Billy,
>
> On Wed 16 Feb 2011 19:06, Billy O'Connor <billyoc@gmail.com> 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 ?? ()

Re: Problem building 2.0 On Ubuntu Maverick

[Andy Wingo]

On Wed 16 Feb 2011 22:58, Billy O'Connor <billyoc@gmail.com> writes:

> 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"

Glad that it worked for you!

If you have time, we would appreciate more details :)  Can you see which
of these options was causing your error?  You can probably safely add -g
to all builds, for better backtraces; I doubt it will affect the
results.

Also, what version of GCC are you using?

Thanks,

Andy
-- 
http://wingolog.org/