From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-17315-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 26167 invoked by alias); 20 Feb 2004 00:17:08 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 26153 invoked from network); 20 Feb 2004 00:17:07 -0000
Received: from unknown (HELO localhost.redhat.com) (216.129.200.20)
  by sources.redhat.com with SMTP; 20 Feb 2004 00:17:07 -0000
Received: from gnu.org (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 98A662B92; Thu, 19 Feb 2004 19:17:03 -0500 (EST)
Message-ID: <403551FF.70401@gnu.org>
Date: Fri, 20 Feb 2004 00:17:00 -0000
From: Andrew Cagney <cagney@gnu.org>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.4.1) Gecko/20040217
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: 32-bit gcore on amd64
References: <403542D6.2070603@gnu.org> <20040219232407.GA472@nevyn.them.org>
In-Reply-To: <20040219232407.GA472@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-02/txt/msg00267.txt.bz2

> On Thu, Feb 19, 2004 at 06:12:22PM -0500, Andrew Cagney wrote:
> 
>>> This is more questions than answers.  I'm trying to figure out how GDB 
>>> should generate 32-bit core files on amd64 (i.e., get gmake check 
>>> 'RUNTESTFLAGS=--target_board=unix/-m32 gcore.exp' to pass).  The problem 
>>> is, everything I look at feels wrong.
>>> 
>>> Here's the first backtrace:
>>> 
>>> #0  amd64_collect_native_gregset (regcache=0x808410, gregs=0x7fbfffead0,
>>>     regnum=-1) at /home/cygnus/cagney/GDB/src/gdb/amd64-nat.c:124
>>> #1  0x0000000000450e16 in fill_gregset (gregsetp=0x808410, 
>>> regnum=-1073747248)
>>>     at /home/cygnus/cagney/GDB/src/gdb/x86-64-linux-nat.c:126
>>> #2  0x000000000045803d in linux_do_thread_registers (obfd=0x87fc90, ptid=
>>>       {pid = 10494, lwp = 10494, tid = 0}, note_data=0x8b0960 "\005",
>>>     note_size=0x7fbfffed8c) at 
>>> /home/cygnus/cagney/GDB/src/gdb/linux-proc.c:180
>>> 
>>> This function is asking fill_gregset to populate an amd64 gregset_t.  I 
>>> think it should be asking for the 32-bit gregset_t to be filled in.
> 
> 
> Does the same thing apply to mips64-linux/-mabi=32?  Normally we make a
> point of only dealing with the registers' "real" size.

"Possibly", can you clarify this a little?

GDB debugging a 32-bit i386 program should always "gcore" a 32-bit i386 
core file.

Andrew