Bug#561203: FTBFS [hppa] - build hangs
Hello,
On antradienis 15 Gruodis 2009 18:29:58 dann frazier wrote:
> > On antradienis 15 Gruodis 2009 07:32:08 dann frazier wrote:
> > > Source: kde4libs
> > > Version: 4:4.3.4-1
> > > Severity: serious
> > > User: debian-h...@lists.debian.org
> > > Usertags: hppa
> > >
> > > kde4libs hangs during build on hppa, but the hang location varies.
> >
> > Doesn't this evidence suggest that either c++ toolchain, hardware, kernel
> > etc. is broken on hppa in general / on peri? automoc4 has not been
> > rebuilt for half a year and numerous previous kde4libs versions have
> > built successfully since then...
>
> Yes, it certainly does. The hppa porters are looking into such issues,
> using the above usertag as a todo list.
To reproduce:
$ cat minifail.cpp
#include
#include
int main(int argc, char** argv) {
QCoreApplication app(argc, argv);
QProcess proc;
proc.start("/usr/bin/cut", QStringList(), QIODevice::NotOpen);
proc.waitForFinished(-1);
return 0;
}
$ g++-4.4 -I/usr/include/qt4 -lQtCore minifail.cpp -o minifail
$ i=0; while true; do i=$(($i+1)); echo Run $i; ./minifail; done
Run 1
Run 2
Run 3
Run 4
Run 5
Run 6
Run 7
Run 8
Run 9
Run 10
$ ps aux | grep ...
modax11058 0.0 0.0 19728 3020 pts/1Sl+ 08:45 0:00 ./minifail
modax11060 0.0 0.0 0 0 pts/1Z+ 08:45 0:00 [cut]
$ gdb -p 11058
(gdb) bt
#0 0x4082fe30 in select () from /lib/libc.so.6
#1 0x405d9644 in qt_native_select (fdread=0xfb091410, fdwrite=0xfb091490,
timeout=) at io/qprocess_unix.cpp:936
#2 0x405dc3ac in QProcessPrivate::waitForFinished (this=0x27f80, msecs=-1) at
io/qprocess_unix.cpp:1158
#3 0x4058b6f8 in QProcess::waitForFinished (this=0xfb0912dc, msecs=-1) at
io/qprocess.cpp:1318
#4 0x00010f24 in main ()
(gdb)
Frame #1 is at
http://qt.gitorious.org/qt/qt/blobs/4.5/src/corelib/io/qprocess_unix.cpp#line1158
Sometimes minifail crashes:
$ i=0; while true; do i=$(($i+1)); echo Run $i; ./minifail; done;
Run 1
Run 2
Run 3
Run 4
Run 5
Run 6
Run 7
Run 8
Run 9
Run 10
Run 11
Run 12
Run 13
Run 14
Segmentation fault
Run 15
Run 16
Segmentation fault
Run 17
Run 18
Run 19
Run 20
Run 21
Run 22
Run 23
Run 24
Run 25
Run 26
Run 27
Run 28
Run 29
Run 30
Run 31
Run 32
Run 33
Run 34
Run 35
So repeatedly running it under gdb I see a couple of SIGSEGVs:
$ gdb ./minifail
GNU gdb (GDB) 7.0-debian
Reading symbols from /home/modax/minifail...(no debugging symbols
found)...done.
(gdb) r
Starting program: /home/modax/minifail
[Thread debugging using libthread_db enabled]
[New Thread 0x41b5c480 (LWP 15889)]
[Thread 0x41b5c480 (LWP 15889) exited]
Program exited normally.
(gdb)
(gdb) r
Starting program: /home/modax/minifail
[Thread debugging using libthread_db enabled]
[New Thread 0x41b5c480 (LWP 15892)]
[Thread 0x41b5c480 (LWP 15892) exited]
Program exited normally.
(gdb)
(gdb) r
Starting program: /home/modax/minifail
[Thread debugging using libthread_db enabled]
[New Thread 0x41b5c480 (LWP 15895)]
[Thread 0x41b5c480 (LWP 15895) exited]
Program exited normally.
(gdb) r
Starting program: /home/modax/minifail
[Thread debugging using libthread_db enabled]
[New Thread 0x41b5c480 (LWP 15909)]
[Thread 0x41b5c480 (LWP 15909) exited]
Program exited normally.
(gdb) r
Starting program: /home/modax/minifail
[Thread debugging using libthread_db enabled]
[New Thread 0x41b5c480 (LWP 15912)]
[Thread 0x41b5c480 (LWP 15912) exited]
Program exited normally.
(gdb) r
Starting program: /home/modax/minifail
[Thread debugging using libthread_db enabled]
[New Thread 0x41b5c480 (LWP 15915)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x41b5c480 (LWP 15915)]
0x in ?? ()
(gdb) bt
#0 0x in ?? ()
#1 0x in ?? ()
(gdb) r
Bug#561203: FTBFS [hppa] - build hangs
On Tue, Dec 15, 2009 at 06:12:45PM +0200, Modestas Vainius wrote: > Hello, > > On antradienis 15 Gruodis 2009 07:32:08 dann frazier wrote: > > Source: kde4libs > > Version: 4:4.3.4-1 > > Severity: serious > > User: debian-h...@lists.debian.org > > Usertags: hppa > > > > kde4libs hangs during build on hppa, but the hang location varies. > > Doesn't this evidence suggest that either c++ toolchain, hardware, kernel > etc. > is broken on hppa in general / on peri? automoc4 has not been rebuilt for > half > a year and numerous previous kde4libs versions have built successfully since > then... Yes, it certainly does. The hppa porters are looking into such issues, using the above usertag as a todo list. -- dann frazier -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561203: FTBFS [hppa] - build hangs
Hello, On antradienis 15 Gruodis 2009 07:32:08 dann frazier wrote: > Source: kde4libs > Version: 4:4.3.4-1 > Severity: serious > User: debian-h...@lists.debian.org > Usertags: hppa > > kde4libs hangs during build on hppa, but the hang location varies. Doesn't this evidence suggest that either c++ toolchain, hardware, kernel etc. is broken on hppa in general / on peri? automoc4 has not been rebuilt for half a year and numerous previous kde4libs versions have built successfully since then... -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
Bug#561203: FTBFS [hppa] - build hangs
Source: kde4libs Version: 4:4.3.4-1 Severity: serious User: debian-h...@lists.debian.org Usertags: hppa kde4libs hangs during build on hppa, but the hang location varies. First attempt: [...] [ 48%] Generating org.kde.kded.xml cd kded && /usr/bin/qdbuscpp2xml /build/buildd/kde4libs-4.3.4/kded/kdedadaptor.h > /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kded/org.kde.kded.xml qdbuscpp2xml: exit code 0 from moc. Aborting QProcess: Destroyed while process is still running. make[3]: *** Deleting file `kded/org.kde.kded.xml' make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. make[2]: *** [kded/CMakeFiles/kdeinit_kded4.dir/all] Error 2 make[1]: *** [all] Terminated make: *** [debian/stamp-makefile-build] Terminated Build killed with signal 15 after 300 minutes of inactivity Second attempt: [...] make[3]: Entering directory `/build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu' cd kio && /usr/bin/automoc4 /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kio/kio_automoc.cpp /build/buildd/kde4libs-4.3.4/kio /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kio /usr/bin/moc-qt4 /usr/bin/cmake Generating kdirwatch_p.moc make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. make[2]: *** [kio/CMakeFiles/kio_automoc.dir/all] Error 2 make[1]: *** [all] Terminated make: *** [debian/stamp-makefile-build] Terminated Build killed with signal 15 after 300 minutes of inactivity The third attempt is currently hung at: [...] make[3]: Entering directory `/build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu' cd kdecore && /usr/bin/automoc4 /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore/kdecore_automoc.cpp /build/buildd/kde4libs-4.3.4/ kdecore /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore /usr/bin/moc-qt4 /usr/bin/cmake Generating klibrary.moc The build system looks wedged - it isn't consuming any cpu. The build-related processes are: buildd4199 766 0 02:53 ?00:00:00 /usr/bin/make -C obj-hppa-linux-gnu buildd4212 4199 0 02:53 ?00:00:00 /usr/bin/make -f CMakeFiles/Makefile2 all buildd5739 4212 0 02:55 ?00:00:00 /usr/bin/make -f kdecore/CMakeFiles/kdecore_automoc.dir/build.make kdecore/CMakeFiles/kdecore_automoc.dir/build buildd5740 5739 0 02:55 ?00:00:00 /bin/sh -c cd kdecore && /usr/bin/automoc4 /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore/kdecore_automoc.cpp /build/buildd/kde4libs-4.3.4/kdecore /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore /usr/bin/moc-qt4 /usr/bin/cmake buildd5741 5740 0 02:55 ?00:00:00 /usr/bin/automoc4 /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore/kdecore_automoc.cpp /build/buildd/kde4libs-4.3.4/kdecore /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore /usr/bin/moc-qt4 /usr/bin/cmake buildd5755 5741 0 02:56 ?00:00:00 [cmake] strace shows that automoc4 is stuck in a select call: Process 5741 attached - interrupt to quit _newselect(1024, [10], [], NULL, NULL -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
