Hi all,
I'm puzzled that, in a rebuild of all my pkgs in build-order (for a
whim, let's say.. :)),
qt4-x11 fails systematically with a seg-fault on 32bit (10.5.8,
core2duo,
all the rest up to date, including X11-2.5.2) _ and doesn't on 64bit.
This is so as well if I remove fink's make with force-depends. Of
course,
/usr/bin/make and %p/bin/make have the same %v, 3.81, but it would
have been conceivable
that seg-faults disappear with slight variations in %c etc..
The above implies implies that qt4-x11 was previously built successfully
in essentially the same environment (except of course probably
X11-2.5.1).
In the log of the previous succesfull build (Feb 23) I have :
cd src/corelib/ && make -f Makefile
/sw32/bld/qt4-x11-4.6.2-2/qt-kde-qt-mac/bin/moc -DQT_SHARED -
D__USE_WS_X11__ -DQT_BUILD_CORE_LIB -DQT_NO_USING_NAMESPACE -
DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT -
DQT_MOC_COMPAT -DHB_EXPORT=Q_CORE_EXPORT -DQT_NO_DEBUG -
D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I../../mkspecs/darwin-g++42 -
I. -I../../include -I../../include/QtCore -I.rcc/release-shared -
Iglobal -I../3rdparty/harfbuzz/src -I../3rdparty/md5 -I../3rdparty/md4
-I.moc/release-shared animation/qabstractanimation.h -o .moc/release-
shared/moc_qabstractanimation.cpp
while the new build gives, adding manually"-d" to the make flags
(and ommitting a huge amount of info before the "..."):
> cd src/corelib/ && make -f Makefile
> ...
> Pruning file `animation/qabstractanimation.h'.
> Finished prerequisites of target file `.moc/release-shared/
> moc_qabstractanimation.cpp'.
> Must remake target `.moc/release-shared/
> moc_qabstractanimation.cpp'.
> /sw32/bld/qt4-x11-4.6.2-2/qt-kde-qt-mac/bin/moc -DQT_SHARED -
> D__USE_WS_X11__ -DQT_BUILD_CORE_LIB -DQT_NO_USING_NAMESPACE -
> DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT -
> DQT_MOC_COMPAT -DHB_EXPORT=Q_CORE_EXPORT -DQT_NO_DEBUG -
> D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I../../mkspecs/darwin-g+
> +42 -I. -I../../include -I../../include/QtCore -I.rcc/release-shared
> -Iglobal -I../3rdparty/harfbuzz/src -I../3rdparty/md5 -I../3rdparty/
> md4 -I.moc/release-shared animation/qabstractanimation.h -o .moc/
> release-shared/moc_qabstractanimation.cpp
> Putting child 0x0026ecd0 (.moc/release-shared/
> moc_qabstractanimation.cpp) PID 49180 on the chain.
> Live child 0x0026ecd0 (.moc/release-shared/
> moc_qabstractanimation.cpp) PID 49180
> Reaping losing child 0x0026ecd0 PID 49180
> make: *** [.moc/release-shared/moc_qabstractanimation.cpp]
> Segmentation fault
> Removing child 0x0026ecd0 PID 49180 from chain.
so the "moc" commands are identical, and the relevant args to this
Makefile seem so too...
Of course, to compare Makefiles, the old build-dir is lost, and I
wouldn't know how to
re-create it safely, since so many things have changed in the meantime..
Crashreporter is not of much help:
# cat /Library/Logs/CrashReporter/make_2010-07-29-093117_jfm-2.crash
Process: make [55072]
Path: make
Identifier: make
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: make [55067]
Date/Time: 2010-07-29 09:31:17.677 +0200
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: ABB34E0D-89DB-4174-8999-2CA574C5ABB7
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: Unknown
Backtrace not available
Unknown thread crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x00000000 ecx: 0x00000000 edx: 0x00000000
edi: 0x00000000 esi: 0x00000000 ebp: 0x00000000 esp: 0x00000000
ss: 0x0000001f efl: 0x00010202 eip: 0x00000000 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x0000001f
cr2: 0x00000000
Binary images description not available
(essentially the same with both make's)
Don't know how get about this ...
Even a diff with "-d" shows little relevant info (w/o "-d" even much
less):
# diff -ud /sw/var/logs/qt4-x11.log*|more
--- /sw/var/logs/qt4-x11.log 2010-02-23 18:03:40.000000000 +0100
+++ /sw/var/logs/qt4-x11.log_new 2010-07-29 09:59:05.000000000
+0200
...
@@ -45,7 +58,7 @@
Determining system architecture... (Darwin:9.8.0:i386)
'macosx' is supported
System architecture: 'macosx'
-Separate debug info support disabled.
+Separate debug info support enabled.
This is the Qt for Linux/X11 Open Source Edition.
...
@@ -2320,7 +2333,7 @@
mitshm enabled.
FontConfig auto-detection... ()
c++ -c -pipe -O2 -Wall -W -D__USE_WS_X11__ -I../../../mkspecs/darwin-g+
+42 -I. -I/sw32/lib/system-openssl/include -I/sw32/lib/freetype219/
include -I/sw32/lib/freetyp
e219/include/freetype2 -I/sw32/lib/fontconfig2/include -I/sw32/include
-I/sw32/include/freetype2 -I/usr/X11/include -I/usr/X11/include/
freetype2 -I/usr/X11/include/fr
eetype2 -I/usr/X11/include -o fontconfig.o fontconfig.cpp
-c++ -prebind -o fontconfig fontconfig.o -L/usr/X11R6/lib -L/sw/lib/
system-openssl/lib -L/sw/lib/freetype219/lib -L/sw/lib/fontconfig2/lib
-L/sw/lib -L/usr/X11R6/l
ib -L/usr/X11/lib -lz -lfreetype -lfontconfig -lXext -lX11 -lm
+c++ -prebind -o fontconfig fontconfig.o -L/usr/X11R6/lib -L/sw/lib/
system-openssl/lib -L/sw/lib/freetype219/lib -L/sw/lib/fontconfig2/lib
-L/sw/lib -L/usr/X11R6/l
ib -L/usr/X11/lib -lfreetype -lfontconfig -lXext -lX11 -lm
FontConfig enabled.
Session Management auto-detection... ()
c++ -c -pipe -O2 -Wall -W -D__USE_WS_X11__ -I../../../mkspecs/darwin-g+
+42 -I. -I/sw32/lib/system-openssl/include -I/sw32/lib/freetype219/
include -I/sw32/lib/freetyp
e219/include/freetype2 -I/sw32/lib/fontconfig2/include -I/sw32/include
-I/usr/X11/include -o sm.o sm.cpp
@@ -2415,6 +2428,7 @@
Stdint auto-detection... ()
c++ -c -pipe -O2 -Wall -W -D__USE_WS_X11__ -D_LARGEFILE64_SOURCE -
D_LARGEFILE_SOURCE -I../../../mkspecs/darwin-g++42 -I. -I/sw32/lib/
system-openssl/include -I/sw32/l
ib/freetype219/include -I/sw32/lib/freetype219/include/freetype2 -I/
sw32/lib/fontconfig2/include -I/sw32/include -o main.o main.cpp
c++ -prebind -o stdint main.o -L/sw/lib/system-openssl/lib -L/sw/
lib/freetype219/lib -L/sw/lib/fontconfig2/lib -L/sw/lib -L/usr/X11R6/lib
+(test -z "" || cd "" ; targ=`basename stdint`; objcopy --only-keep-
debug "$targ" "$targ.debug" && objcopy --strip-debug "$targ" &&
objcopy --add-gnu-debuglink="$targ
.debug" "$targ" && chmod -x "$targ.debug" ) ;
Stdint enabled.
This target is using the GNU C++ compiler (darwin-g++42).
@@ -2434,7 +2448,7 @@
qmake vars .......... cat: .qmake.vars: No such file or directory
qmake switches ......
Build ............... libs tools docs
-Configuration ....... release shared dll largefile stl mmx 3dnow sse
sse2 absolute_library_soname minimal-config small-config medium-
config large-config full-confi
g qt3support phonon phonon-backend accessibility opengl reduce_exports
ipv6 getaddrinfo ipv6ifname getifaddrs system-jpeg system-mng system-
png png gif system-tiff sy
stem-freetype system-zlib nis cups iconv glib gstreamer dbus dbus-
linked openssl-linked x11sm xshape xsync xrender mitshm fontconfig xkb
xmlpatterns multimedia audio-
backend svg webkit script scripttools release
+Configuration ....... release shared dll largefile stl
separate_debug_info mmx 3dnow sse sse2 absolute_library_soname
minimal-config small-config medium-config lar
ge-config full-config qt3support phonon phonon-backend accessibility
opengl reduce_exports ipv6 getaddrinfo ipv6ifname getifaddrs system-
jpeg system-mng system-png pn
g gif system-tiff system-freetype system-zlib nis cups iconv glib
gstreamer dbus dbus-linked openssl-linked x11sm xshape xsync xrender
mitshm fontconfig xkb xmlpatter
ns multimedia audio-backend svg webkit script scripttools release
Debug ............... no
Qt 3 compatibility .. yes
QtDBus module ....... yes (linked)
(and in the rest, even "-d" gets lost, and doesn't see anything..)
So, to me, to main difference I see is :
-Separate debug info support disabled.
+Separate debug info support enabled.
Still,
# ls -l /sw/fink/dists/unstable/main/finkinfo/x11/qt4-x11*
-rw-r--r-- 1 root admin 10409 Feb 23 15:00 /sw/fink/dists/unstable/
main/finkinfo/x11/qt4-x11.info
-rw-r--r-- 1 root admin 11283 Feb 22 20:13 /sw/fink/dists/unstable/
main/finkinfo/x11/qt4-x11.patch
So the info and patch files didn't change since the last succesfull
builds ...
What might have caused the "Separate debug info support" to change ?
(And it might be nice to be able to test this with anoher "make"...)
Does anybody have an idea what might have caused a change
in the build-parameters ("debug info support disabled")
of qt4-x11 ?
Can anybody reproduce this (seems hard _ on an ~identical
fink installation in 64bit onn the same machine I can't..)
And how to go about pinning down this problem ?
Jean-Francois
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
