Bug 9507 - x86-32 address calculations on x86-64 are incorrect
Summary: x86-32 address calculations on x86-64 are incorrect
Status: RESOLVED DUPLICATE of bug 9508
Alias: None
Product: gdb
Classification: Unclassified
Component: exp (show other bugs)
Version: unknown
: P3 enhancement
Target Milestone: ---
Assignee: Daniel Jacobowitz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-10 19:18 UTC by mostrows
Modified: 2008-12-18 20:56 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mostrows 2008-01-10 19:18:01 UTC
[Converted from Gnats 2402]

I try to access some target program symbols and fail:

(gdb) p buf
multi-thread:target_xfer_partial (2, (null), 0x299f020,  0x0,  0x1ff960950, 4) = 0
Cannot access memory at address 0xff960950

Note that gdb is trying to look up address 0x1ff960950, not
0xff960950.  Obviously this fails as it is not a 32-bit address that is valid in this program.

The addition that overflows the 32-bit address space is at findvar.c:496.

Release:
unknown

Environment:
This occurs when debugging 32-bit application on 64-bit
Linux systems.
Comment 1 Daniel Jacobowitz 2008-01-11 02:22:25 UTC
*** This bug has been marked as a duplicate of 9508 ***