From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: 32-bit gcore on amd64
Date: Thu, 19 Feb 2004 23:24:00 -0000 [thread overview]
Message-ID: <20040219232407.GA472@nevyn.them.org> (raw)
In-Reply-To: <403542D6.2070603@gnu.org>
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.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-19 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 23:12 Andrew Cagney
2004-02-19 23:24 ` Daniel Jacobowitz [this message]
2004-02-20 0:17 ` Andrew Cagney
2004-02-21 2:25 ` Daniel Jacobowitz
2004-02-20 19:59 ` Mark Kettenis
2004-02-20 21:06 ` Andrew Cagney
2004-02-20 23:44 ` Mark Kettenis
2004-02-19 23:47 Ulrich Weigand
2004-02-20 18:56 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040219232407.GA472@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox