From owner-freebsd-emulation@FreeBSD.ORG  Wed Jan 19 16:58:45 2005
Return-Path: <owner-freebsd-emulation@FreeBSD.ORG>
Delivered-To: freebsd-emulation@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0CD7016A4CE; Wed, 19 Jan 2005 16:58:45 +0000 (GMT)
Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2A75743D1F; Wed, 19 Jan 2005 16:58:44 +0000 (GMT)
	(envelope-from killing@multiplay.co.uk)
Received: from vader ([212.135.219.179])
	by multiplay.co.uk (multiplay.co.uk [212.42.16.7])
	(MDaemon.PRO.v7.2.2.R)
	with ESMTP id md50000889568.msg;
	Wed, 19 Jan 2005 16:47:55 +0000
Message-ID: <00b301c4fe47$f81fc020$b3db87d4@multiplay.co.uk>
From: "Steven Hartland" <killing@multiplay.co.uk>
To: <emulation@FreeBSD.org>, <freebsd-hackers@freebsd.org>
Date: Wed, 19 Jan 2005 16:57:12 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-Spam-Processed: multiplay.co.uk, Wed, 19 Jan 2005 16:47:55 +0000
	(not processed: message from valid local sender)
X-MDRemoteIP: 212.135.219.179
X-Return-Path: killing@multiplay.co.uk
X-MDAV-Processed: multiplay.co.uk, Wed, 19 Jan 2005 16:47:59 +0000
Subject: Debugging linux emulation how?
X-BeenThere: freebsd-emulation@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Development of Emulators of other operating systems
	<freebsd-emulation.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>,
	<mailto:freebsd-emulation-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-emulation>
List-Post: <mailto:freebsd-emulation@freebsd.org>
List-Help: <mailto:freebsd-emulation-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>,
	<mailto:freebsd-emulation-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2005 16:58:45 -0000

I've got a linux app who's data in a tcp steam appears to be
getting jumbled. The same app on linux performs correct so
I need a way of looking at the data in the calls going through
the ABI. truss only seems to show a call linux_socketcall
which looking at the ABI code does indeed hand off to
linux_socket if appropriate.

What's the best way of tracing this? Can I add debug lines
into the linux kernel module if so what would this look like?

Note: This is remote machine so serial debugging would
not be an option.

    Steve


================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to postmaster@multiplay.co.uk.