From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18058 invoked by alias); 16 May 2002 22:43:32 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18040 invoked from network); 16 May 2002 22:43:30 -0000 Received: from unknown (HELO neptune.kirkland.local) (12.104.72.61) by sources.redhat.com with SMTP; 16 May 2002 22:43:30 -0000 Received: by neptune.kirkland.local with Internet Mail Service (5.5.2650.21) id ; Thu, 16 May 2002 15:43:28 -0700 Message-ID: <43CB1396676FD4119F03001083FD2994F5F225@neptune.kirkland.local> From: "Kevin \"Squail\" Endres" To: 'Kevin Buettner' , "Kevin \"Squail\" Endres" , 'Daniel Jacobowitz' , Richard.Earnshaw@arm.com Cc: gdb@sources.redhat.com Subject: RE: cross targeted gdb and corefiles Date: Thu, 16 May 2002 15:43:00 -0000 MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2002-05/txt/msg00204.txt.bz2 ahh - so i need to find out what gregset_t and fpregset_t should be.... any hits where to look?? :]k -----Original Message----- From: Kevin Buettner [mailto:kevinb@redhat.com] Sent: Thursday, May 16, 2002 3:33 PM To: Kevin "Squail" Endres; 'Kevin Buettner'; 'Daniel Jacobowitz'; Richard.Earnshaw@arm.com Cc: gdb@sources.redhat.com Subject: Re: cross targeted gdb and corefiles On May 16, 3:27pm, Kevin \Squail\ Endres wrote: > Yep had just figured out to move the supply_* (and the nwfpe*) functions > from arm-linux-nat.c to arm-linux-tdep.c. I did assume that the kernel > headers needed to be from an arm configured kernel so i set the prefix to > the root of my cross toolchain whemn i configured. > > everything builds but when i try to read an arm core i get a warning about > the size of the gregset struct in the core (so possibly i am truly not > including the correct headers??) The trick is to not depend on the headers at all. One way to do this is to define (in the tdep.c file) the necessary structs entirely in terms of chars. (This includes adding in any ABI mandated padding between fields.) Kevin