Package: beast
Version: 0.6.6-5

lt-zintern produces an exception when I compile it with a snapshot of
GCC 4.2.  I'm not entirely sure whether this is a compiler bug or one
in your package, but from other cases like these it is likely that
your package is doing something wrong and that changes in the compiler
only exhibit the problem.

The interesting thing is that it still fails even after I drop all
optimization from the package.  Do you think you can inestigate?  You
can reproduce this with the gcc-snapshot package.


> Automatic build of beast_0.6.6-5 on test.track.rz.uni-augsburg.de by 
> sbuild/powerpc 0.44
...
> creating zintern
> ./zintern -b -z wave-mono ./wave-mono.bse gus-patch ./gus-patch.bse > 
> xgen-bzc                                        \
>       && echo "static const BseZFile bse_zfiles[] = {" >> xgen-bzc            
>         \
>       && for i in wave-mono gus-patch ; do                            \
>               uname=$(echo $i | tr a-z- A-Z_);                                
>         \
>               echo "  { \"$i\", $uname""_SIZE, "      >>xgen-bzc;             
>         \
>               echo "    $uname""_DATA, G_N_ELEMENTS ($uname""_DATA) }," 
> >>xgen-bzc;   \
>       done                                                                    
>         \
>       && echo "};" >> xgen-bzc                                                
>         \
>       && cp xgen-bzc bse-zfile.c                                              
>                 \
>       && rm -f xgen-bzc
> /bin/sh: line 9: 17972 Trace/breakpoint trap   ./zintern -b -z wave-mono 
> ./wave-mono.bse gus-patch ./gus-patch.bse >xgen-bzc
> make[4]: *** [bse-zfile.c] Error 133


Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread -134421504 (LWP 4706)]
sfi_msg_type_register (ident=0xffdb218 "none", default_ouput=SFI_MSG_NONE, 
label=0x0) at sfilog.c:205
205           sfi_atomic_pointer_set (guint8*, &sfi_msg_flags, msg_flags);
(gdb) where
#0  sfi_msg_type_register (ident=0xffdb218 "none", default_ouput=SFI_MSG_NONE, 
label=0x0)
    at sfilog.c:205
#1  0x0ffca564 in sfi_msg_type_init_internals () at sfilog.c:67
#2  0x0ffcaba4 in sfi_msg_type_register (ident=0xffdbb6c "comport", 
default_ouput=SFI_MSG_DEBUG,
    label=0x0) at sfilog.c:170
#3  0x0ffd0fa0 in __sfi_msg_type__init34__debug_comport () at sficomport.c:34
#4  0x0ffd4e34 in __do_global_ctors_aux () from 
/home/tbm/src/beast-0.6.6/sfi/.libs/libsfi-0.6.so.6
#5  0x0ff84d0c in _init () from 
/home/tbm/src/beast-0.6.6/sfi/.libs/libsfi-0.6.so.6
#6  0xf7ff20d0 in _dl_rtld_di_serinfo () from /lib/ld.so.1
#7  0xf7ff20d0 in _dl_rtld_di_serinfo () from /lib/ld.so.1
#8  0xf7ff20d0 in _dl_rtld_di_serinfo () from /lib/ld.so.1
Previous frame inner to this frame (corrupt stack?)
(gdb)

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to