I was hoping someone with more familiarity with x86/x86-64 would comment on it.
In any case, when I looked at the patch, it seemed to me that MAP32_BIT is going to be used unconditionally for all platforms that define such a macro. That seems wrong to me. You don't want to force mapping in the low 4GiB for 64-bit targets (you could easily run out of address space). Did I miss something? --david On 5/1/07, Nurdin Premji <[EMAIL PROTECTED]> wrote:
Nurdin Premji wrote: > Can this be committed? This forces the memory mapped in from the inferior process to be mapped only into the first 32 bits of memory. This avoids the situation of truncated memory addresses when unwinding a 32 bit process on a 64 bit host. _______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
-- Mosberger Consulting LLC, http://www.mosberger-consulting.com/ _______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
