This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/20758] New: 32-bit gdb on 64-bit kernel
- From: "pangbw at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 01 Nov 2016 20:33:22 +0000
- Subject: [Bug gdb/20758] New: 32-bit gdb on 64-bit kernel
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20758
Bug ID: 20758
Summary: 32-bit gdb on 64-bit kernel
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: pangbw at gmail dot com
Target Milestone: ---
I am asking a question as I am not sure this is a bug or not in GDB:
Is the combination of 32-bit gdb and 64-bit kernel valid?
I see such code in gdb:
ppc_register_u_addr (struct gdbarch *gdbarch, int regno)
{
unsigned long long u_addr = -1;
struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch);
/* NOTE: cagney/2003-11-25: This is the word size used by the ptrace
interface, and not the wordsize of the program's ABI. */
int wordsize = sizeof (long);
The result of sizeof(long) would be different for 32-bit mode and 64-bit mode
which would eventually result the calling to ptrace() fail when the gdb is
32-bit but the kernel is 64-bit mode.
I want to know if this is a bug in gdb we need to fix or this is not a valid
combination as we should not build gdb in 32-bit mode when it will be running
under 64-bit kernel.
--
You are receiving this mail because:
You are on the CC list for the bug.