Your message dated Sun, 4 Mar 2012 12:53:40 +0000
with message-id <20120304125339.ga22...@einval.com>
and subject line Re: Bug#367831: 367831: builds fine on amd64, too
has caused the Debian Bug report #367831,
regarding FTBFS with GCC 4.2: fusebirth segfaults
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
367831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freebirth
Version: 0.3.2-7
fusebirth segfaults (at least on powerpc) 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 newer
optimizations exhibit the problem.
Maybe you or your upstream can investigate. If everything fails, I
can talk to someone who knows GCC well.
I've done some preliminary investigation which shows where the error
is. The segfault goes away if you drop the optimization from
oscillator.c. A traceback shows:
Program received signal SIGSEGV, Segmentation fault.
topo_sort (node=0xffff8008, order=0xfffa2968) at fuse_loops.c:43
43 for (children = node->get_children(node);
(gdb) where
#0 topo_sort (node=0xffff8008, order=0xfffa2968) at fuse_loops.c:43
#1 0x1000dbe8 in topo_sort (node=0x100d80d8, order=0xfffa2968) at
fuse_loops.c:46
#2 0x1000dbe8 in topo_sort (node=0x100d9130, order=0xfffa2968) at
fuse_loops.c:46
#3 0x1000dbe8 in topo_sort (node=0x100da9f0, order=0xfffa2968) at
fuse_loops.c:46
#4 0x1000dbe8 in topo_sort (node=0x100dba88, order=0xfffa2968) at
fuse_loops.c:46
#5 0x1000dbe8 in topo_sort (node=0x100ffbb8, order=0xfffa2968) at
fuse_loops.c:46
#6 0x1000dc70 in fuse_loops (left=0x0, right=0x10100478, file=0x101013e8) at
fuse_loops.c:119
#7 0x10006b44 in main (argc=<value optimized out>, argv=<value optimized out>)
at freebirth.c:134
(gdb)
> Automatic build of freebirth_0.3.2-7 on test.track.rz.uni-augsburg.de by
> sbuild/powerpc 0.44
...
> gcc -g -Wall -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -O2 -c -o
> oscillator.o oscillator.c
...
> gcc -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm
> -lpangocairo-1.0 -lfontconfig -lXext -lXrender -lXinerama -lXi -lXrandr
> -lXcursor -lXfixes -lpango-1.0 -lcairo -lX11 -lgobject-2.0 -lgmodule-2.0 -ldl
> -lglib-2.0 fusebirth.o oscillator.o sequencer.o envelope.o filter.o
> gtkdial.o mixer.o raw_wave.o event.o sample_producer.o blender.o delay.o
> reverb.o all_pass.o delay_panel.o reverb_panel.o multi_tap_delay.o
> sample_freq_strip.o fuse_loops.o -lm -L/usr/lib -lgtk-x11-2.0 -o fusebirth
> ./fusebirth > fused_loop.c 2>/dev/null
> /bin/sh: line 1: 24295 Segmentation fault ./fusebirth >fused_loop.c
> 2>/dev/null
> make[1]: *** [fused_loop.c] Error 139
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
On Sat, Oct 15, 2011 at 01:55:04AM +0100, peter green wrote:
>>fusebirth is only used to generate fused_loop.c, which is then used to
>>build the final freebirth. so shipping a generated fused_loop.c instead
>>of trying to generate it every time would be a solution.
>IMO if this is still an issue building the generator with -O0 would
>be a more appropriate soloution for debian than shipping the
>generated code.
Just tested on a ppc running sid today using gcc 4.6.3 and this builds
just fine. Looks to have been a temporary toolchain problem on ppc,
maybe. Closing.
--
Steve McIntyre, Cambridge, UK. st...@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back
--- End Message ---
