Date: Fri, 11 Jan 2008 13:59:32 GMT From: Jonathan Pascal <jkpyvxmzsa@mailinator.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/119564: [ktrace] kdump segfault on linux binaries Message-ID: <200801111359.m0BDxWOd064649@www.freebsd.org> Resent-Message-ID: <200801111410.m0BEA1IA004830@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 119564 >Category: misc >Synopsis: [ktrace] kdump segfault on linux binaries >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 11 14:10:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Jonathan Pascal >Release: 7.0-BETA3 >Organization: >Environment: FreeBSD foobar 7.0-BETA3 FreeBSD 7.0-BETA3 #8: Wed Jan 9 16:19:57 CET 2008 root@foobar:/usr/obj/usr/src/sys/GENERIC i386 >Description: Debugging Linux binaries is a pain. strace segfaults, kdump too. This bug report is about kdump: Using ktrace on a linux binary and viewing the result often leads to a segfault in kdump. >How-To-Repeat: Steps to reproduce: - install acroread7 from the ports $ ktrace -i acroread $ kdump -> segfault The last line before the segfault is: 22745 bash CALL freebsd6_mmap(0x3,0xbfbfdf20,<invalid>672202704,MAP_SHARED|MAP_PRIVATE|MAP_RENAME|MAP_NORESERVE|MAP_HASSEMAPHORE|MAP_STACK|MAP_NOSYNC,0x2e6f732e,0x68636163,0x646165,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 [and ca. 260000 "0," following] >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200801111359.m0BDxWOd064649>