From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 15 10:46:14 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE0CE16A41F for ; Thu, 15 Sep 2005 10:46:14 +0000 (GMT) (envelope-from barner@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id B742B43D46 for ; Thu, 15 Sep 2005 10:46:13 +0000 (GMT) (envelope-from barner@gmx.de) Received: (qmail invoked by alias); 15 Sep 2005 10:46:12 -0000 Received: from unknown (EHLO zi025.glhnet.mhn.de) [129.187.19.157] by mail.gmx.net (mp033) with SMTP; 15 Sep 2005 12:46:12 +0200 X-Authenticated: #147403 Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id 800BEC116; Thu, 15 Sep 2005 12:48:39 +0200 (CEST) Date: Thu, 15 Sep 2005 12:48:39 +0200 From: Simon Barner To: freebsd-hackers@FreeBSD.org Message-ID: <20050915104839.GC1098@zi025.glhnet.mhn.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5G06lTa6Jq83wMTw" Content-Disposition: inline User-Agent: Mutt/1.5.10i X-Y-GMX-Trusted: 0 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: {get,set}_fsbase, {get,set}_gsbase and Valgrind X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 10:46:15 -0000 --5G06lTa6Jq83wMTw Content-Type: multipart/mixed; boundary="Bn2rw/3z4jIqBvZU" Content-Disposition: inline --Bn2rw/3z4jIqBvZU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Doug, hackers, a user of the valgrind port reported that it crashed due to an unhandled sysarch call (ports/86007). I found out, that this was because of the get_fsbase, set_fsbase, get_gsbase and set_gsbase calls, which were introduced in FreeBSD 6. I'd be happy if somebody could review my attached patch. It's quite possible that it does not make sense at all since I created it by adopting the code for the other cases without having a real clue about what I was doing :-/ Also, since I could not find any documentation for these calls, it would be very nice to know what they are good for, and if programs like valgrind have to take special care of them. Best regards, Simon --Bn2rw/3z4jIqBvZU-- --5G06lTa6Jq83wMTw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDKVGHCkn+/eutqCoRAkVDAJ9DYCkYG6d6cxPKVD82P159wZt4NgCguN05 LQcN2R6OLZuMnMlBH9MHuoc= =GY2F -----END PGP SIGNATURE----- --5G06lTa6Jq83wMTw--