From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9071 invoked by alias); 6 Aug 2007 10:03:40 -0000 Received: (qmail 8961 invoked by uid 22791); 6 Aug 2007 10:03:38 -0000 X-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,FORGED_RCVD_HELO,TW_FP,TW_PX X-Spam-Check-By: sourceware.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (83.160.170.119) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 06 Aug 2007 10:03:36 +0000 Received: from dijkstra.wildebeest.org ([192.168.1.29]) by gnu.wildebeest.org with esmtp (Exim 4.43) id 1IHzTd-0004cw-6D; Mon, 06 Aug 2007 12:06:17 +0200 Subject: Re: Make CoredumpAction use Task.getRegisterBanks() From: Mark Wielaard To: Phil Muldoon Cc: frysk@sourceware.org In-Reply-To: <46B33940.6000005@redhat.com> References: <1185814384.3674.36.camel@dijkstra.wildebeest.org> <46AE238B.5020204@redhat.com> <1185883408.3653.106.camel@dijkstra.wildebeest.org> <46AFD351.6030004@redhat.com> <1186043315.15044.46.camel@dijkstra.wildebeest.org> <46B33940.6000005@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-W3gDFSOQQ7sxCIF32sDg" Date: Mon, 06 Aug 2007 10:03:00 -0000 Message-Id: <1186394612.3766.37.camel@dijkstra.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) X-Spam-Score: -4.4 (----) X-Virus-Checked: Checked by ClamAV on sourceware.org X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00268.txt.bz2 --=-W3gDFSOQQ7sxCIF32sDg Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Content-length: 2081 Hi Phil, I tried to look up the "core file spec" but it seems no such thing exits you just need to grep through binutils, gdb and kernel sources to figure it all out it seems. Actually various searches all seem to finally point to your frysk core file support (You are the expert now!) :) On Fri, 2007-08-03 at 09:18 -0500, Phil Muldoon wrote: > For the FP and fpxregs (which I am writing code for right now), I just=20 > take the entire register buffer and dump it wholesale into the=20 > appropriate note in the core file. ACK. I saw bug #4890. It looks like whether or not the fp and fpx register banks exist in the first place is platform specific. But I guess this is another one of these "what does the kernel dump and how does gdb read it back in" types of questions... > > If we can match up the raw memory for each register bank between > > ptrace/proc and core files from Task that would be ideal. Then the Isa > > can just do the getRegisterByName() mapping. I'll watch your rewrite of > > the core file stuff and see if this makes things easier and clearer (I > > guess it will). > >=20=20=20 > The two requirements needed for core files are: >=20 > 1) Access to the raw memory behind the register via a ByteBuffer > 2) Access to a logical method of getting registers by name, like=20 > getRegisterByName() And it can then provide those back for the core file as Task consumer as right? The question I am trying to answer is whether or not we can move getRegisterBankBuffers() fully into the (ptrace) Task and let the Isa use a call on the Task to provide the getRegisterByName() mapping functionality from bank/numer to register name. Currently Task (or any other Task consumer can) call back into the Isa to get at the actual register banks, which is messy (and will produce the wrong results for core file backed Tasks). So if we can match up the results of Task.getRegisterBanks()/sendrecRegisterBanks() between ptrace/core Task implementations then we could clean the Isa interface up and make the Isa/Task user always get the correct result. Cheers, Mark --=-W3gDFSOQQ7sxCIF32sDg Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQBGtvHvxVhZCJWr9QwRAjBoAKCEE/VGJm5Gvl+YeZRJug1b1JYQMQCbBAtz eNrzxGthB0WG0Vt66jkO4Co= =TJu4 -----END PGP SIGNATURE----- --=-W3gDFSOQQ7sxCIF32sDg--