On Oct 26, 2005, at 6:36 AM, Benjamin Reed wrote:
Martin Costabel wrote:
Gary K Olson wrote:
[warnings snipped]
I am getting all these warnings, too, but the build succeeds anyway.
make[2]: *** [apidox-am-yes] Error 139
This is a segmentation fault. Some binary executable crashed, but
it is not clear from your output which binary this was. There
should be some more information in /tmp/buildlog/kdelibs3-
unified-3.4.3-22.apidox or similar (look at the last file created
there) and in some crash log in ~/Library/Logs/CrashReporter/
Once you know which program crashed, write to the maintainer about
it.
dmacks ran into this last week, the problem is the doxygen executable.
AFAIK the maintainer hasn't been around for a bit; trying to update
it to 1.4.5 is on my TODO but I haven't had a chance to look at it
yet.
The /tmp/buildlog/kdelibs3-unified crashlog did not show anything
that was not already in the buildlog I already submitted. Nor was
there anything in the ~/library/logs/crashreporter. However, /
Library/logs/CrashReporter had a doxygen.crash.log:
Host Name: Macintosh
Date/Time: 2005-10-25 22:17:06.109 -0600
OS Version: 10.4.2 (Build 8C46)
Report Version: 3
Command: doxygen
Path: /sw/bin/doxygen
Parent: sh [1607]
Version: ??? (???)
PID: 1613
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x09ec4620
Thread 0 Crashed:
0 doxygen 0x00109e50 MemberDef::~MemberDef [unified]
() + 256 (crt.c:355)
1 doxygen 0x001b69ac QGList::clear() + 160 (crt.c:355)
2 doxygen 0x000b6770 MemberName::~MemberName [unified]
() + 128 (crt.c:355)
3 doxygen 0x001b69ac QGList::clear() + 160 (crt.c:355)
4 doxygen 0x00339c68 SList<MemberName>::~SList [in-
charge deleting]() + 48 ((null):-1)
5 doxygen 0x003331c8
_static_initialization_and_destruction_0(int, int) + 5816 ((null):-1)
6 dyld 0x8fe109dc ImageLoaderMachO::doTermination
(ImageLoader::LinkContext const&) + 232
7 dyld 0x8fe038ec dyld::runTerminators() + 116
8 libSystem.B.dylib 0x90013a5c __cxa_finalize + 284
9 libSystem.B.dylib 0x90013904 exit + 36
10 doxygen 0x000022d4 _start + 352 (crt.c:249)
11 doxygen 0x00002170 start + 60
Thread 0 crashed with PPC Thread State 64:
srr0: 0x0000000000109e50 srr1:
0x100000000000d030 vrsave: 0x0000000000000000
cr: 0x24000244 xer: 0x0000000000000000 lr:
0x0000000000109df0 ctr: 0x0000000000000007
r0: 0x0000000000109df0 r1: 0x00000000bfffe1e0 r2:
0x00000000a0001fdc r3: 0x0000000009ec4620
r4: 0x0000000000000004 r5: 0x0000000000000001 r6:
0x0000000009fc43b1 r7: 0x000000000000c432
r8: 0x0000000000000001 r9: 0x0000000009fb9a6b r10:
0x0000000000001887 r11: 0x000000000a002004
r12: 0x000000009000604c r13: 0x0000000000000000 r14:
0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000000000000 r17: 0x0000000000000000 r18:
0x0000000000000000 r19: 0x0000000000000000
r20: 0x0000000000000000 r21: 0x0000000000000000 r22:
0x0000000000000000 r23: 0x0000000000000000
r24: 0x0000000000000000 r25: 0x000000008fe53000 r26:
0x0000000000a00060 r27: 0x0000000000000015
r28: 0x0000000000447050 r29: 0x0000000000000003 r30:
0x0000000009fc43d0 r31: 0x0000000000109d68
Binary Images Description:
0x1000 - 0x446fff doxygen /sw/bin/doxygen
0x8fe00000 - 0x8fe51fff dyld 43.1 /usr/lib/dyld
0x90000000 - 0x901a6fff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x901fe000 - 0x90202fff libmathCommon.A.dylib /usr/lib/system/
libmathCommon.A.dylib
It looks like a bad kern address that is being requested by doxygen?
As I am not really familiar with this program, I will have to wait
until Ben or someone else has time to fix this. Of course, my old
version of kde is working fine. I appreciate the quick response Alex
and Ben. Thanks
Gary K Olson
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
