From owner-freebsd-current@FreeBSD.ORG Wed Jul 4 08:41:24 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C7DCF16A400 for ; Wed, 4 Jul 2007 08:41:24 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id A2F2F13C468 for ; Wed, 4 Jul 2007 08:41:24 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 119FC62E7 for ; Wed, 4 Jul 2007 04:22:48 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 04 Jul 2007 04:22:48 -0400 X-Sasl-enc: yhPrUd2Zqe+jcseG9s/F8gK6xHnPILYKN9KwdUuoIxS1 1183537367 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id 52BB82463 for ; Wed, 4 Jul 2007 04:22:47 -0400 (EDT) Message-ID: <468B589D.3050109@freebsd.org> Date: Wed, 04 Jul 2007 01:21:49 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ptrace, freebsd and vmware dont get along? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2007 08:41:24 -0000 using -current... gdb does not seem to get along well under vmware... doing "gdb a.out" with a "break main" followed by "run" results in the behaviour seen here: ... ptrace(0x21,0xebbe,0xbfbfdc90,0x0,0x28277130) = 0 (0x0) ptrace(0x25,0xebbe,0xbfbfddd4,0x0,0x8) = 0 (0x0) ptrace(0x7,0xebbe,0x1,0x14,0x10202) = 0 (0x0) wait4(0xffffffff,0xbfbfdf08,0x0,0x0,0x28369569) = 60350 (0xebbe) kill(60350,0) = 0 (0x0) ptrace(0x21,0xebbe,0xbfbfdc90,0x0,0x28277130) = 0 (0x0) ptrace(0x25,0xebbe,0xbfbfddd4,0x0,0x8) = 0 (0x0) ptrace(0x7,0xebbe,0x1,0x14,0x10202) = 0 (0x0) wait4(0xffffffff,0xbfbfdf08,0x0,0x0,0x28369569) = 60350 (0xebbe) kill(60350,0) = 0 (0x0) ptrace(0x21,0xebbe,0xbfbfdc90,0x0,0x28277130) = 0 (0x0) ptrace(0x25,0xebbe,0xbfbfddd4,0x0,0x8) = 0 (0x0) ptrace(0x7,0xebbe,0x1,0x14,0x10202) = 0 (0x0) wait4(0xffffffff,0xbfbfdf08,0x0,0x0,0x28369569) = 60350 (0xebbe) kill(60350,0) = 0 (0x0) ptrace(0x21,0xebbe,0xbfbfdc90,0x0,0x28277130) = 0 (0x0) ptrace(0x25,0xebbe,0xbfbfddd4,0x0,0x8) = 0 (0x0) ... and gdb goes out to lunch without returning. And with a ^C, I get it all nice and hung up: 60349 p0- TX 0:27.46 gdb a.out 60350 p0- TX 0:15.39 /bin/csh -c exec /usr/home/darrenr/a.out 60369 p4 I+ 0:00.20 truss -p 60349 It requires a "kill -9" on the truss to restore life. Does anyone have any ideas about where to start trying to resolve this problem? Thanks, Darren