From owner-freebsd-openoffice@FreeBSD.ORG Sun Aug 1 20:43:32 2004 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3E1E16A4CE for ; Sun, 1 Aug 2004 20:43:32 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBB2643D55 for ; Sun, 1 Aug 2004 20:43:31 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i71KhUQW061228 for ; Sun, 1 Aug 2004 22:43:31 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: openoffice@freebsd.org From: Poul-Henning Kamp Date: Sun, 01 Aug 2004 22:43:30 +0200 Message-ID: <61227.1091393010@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: OO1.1.2 + current debugging info on "junk pointer, too high" X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Aug 2004 20:43:32 -0000 I ran a ktrace with the phkmalloc utrace code activated and found the "pointer" it complains about: 60796 setup.bin CALL utrace(0xbfacb680,0xc) 60796 setup.bin USER 12 00 d0 0f 08 00 00 00 00 00 08 00 00 60796 setup.bin RET utrace 0 60796 setup.bin CALL utrace(0xbfacb680,0xc) 60796 setup.bin USER 12 00 e4 0f 08 00 00 00 00 00 08 00 00 60796 setup.bin RET utrace 0 60796 setup.bin CALL issetugid 60796 setup.bin RET issetugid 0 60796 setup.bin CALL getuid 60796 setup.bin RET getuid 488/0x1e8 60796 setup.bin CALL getgid 60796 setup.bin RET getgid 488/0x1e8 60796 setup.bin CALL write(0x2,0xbfbfe8eb,0x9) 60796 setup.bin GIO fd 2 wrote 9 bytes "setup.bin" 60796 setup.bin RET write 9 60796 setup.bin CALL write(0x2,0x29250a1b,0xb) 60796 setup.bin GIO fd 2 wrote 11 bytes " in free():" 60796 setup.bin RET write 11/0xb 60796 setup.bin CALL write(0x2,0x29250924,0xa) 60796 setup.bin GIO fd 2 wrote 10 bytes " warning: " 60796 setup.bin RET write 10/0xa 60796 setup.bin CALL write(0x2,0x29250a80,0x25) 60796 setup.bin GIO fd 2 wrote 37 bytes "junk pointer, too high to make sense " 60796 setup.bin RET write 37/0x25 60796 setup.bin CALL utrace(0xbfacb680,0xc) 60796 setup.bin USER 12 6e 5f 55 53 00 00 00 00 00 08 00 00 ^^^^^^^^^^^ this corresponds to ascii "n_US" and is clearly not a pointer. This happens in a child process which is most likely trying to execute the gnomeint program as the fork happens right after this (slightly bogus) lookup sequence: 60726 setup.bin NAMI "/sbin//usr/local/OpenOffice.org1.1.2/program/gnomeint" 60726 setup.bin NAMI "/usr/sbin//usr/local/OpenOffice.org1.1.2/program/gnomeint" 60726 setup.bin NAMI "/bin//usr/local/OpenOffice.org1.1.2/program/gnomeint" 60726 setup.bin NAMI "/usr/bin//usr/local/OpenOffice.org1.1.2/program/gnomeint" 60726 setup.bin NAMI "/usr/local/bin//usr/local/OpenOffice.org1.1.2/program/gnomeint" 60726 setup.bin NAMI "/usr/X11R6/bin//usr/local/OpenOffice.org1.1.2/program/gnomeint" 60726 setup.bin NAMI "/home/phk/bin//usr/local/OpenOffice.org1.1.2/program/gnomeint" 60726 setup.bin NAMI "/usr/local/OpenOffice.org1.1.0/program//usr/local/OpenOffice.org1.1.2/program/gnomeint " What will it take to get this problem fixed ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.