Re: unaligned access using bash on glibc 2.5
"John David Anglin" <[email protected]>
| Newsgroups | gmane.linux.ports.hppa |
|---|---|
| Message-ID | <[email protected]> |
> Carlos O'Donell a écrit : > > On 5/1/07, Aurelien Jarno <[email protected]> wrote: > >> We have just switched to a glibc 2.5 using LT + TLS in Debian. This > >> causes unaligned memory access when using bash: > >> > >> bash(19279): unaligned access to 0x000e1bb2 at ip=0x407cb76b > > > > Why doesn't this ip match the runtime disassembly you have below? > > Well I don't really now. The address return by the kernel is not > aligned, so that's strange. Note that this does not correspond to the > same execution. I run it once to get the entry in the kernel log, and > once with unaligned=signal to get the SIGBUS in gdb. The two least significant bits in ip contain the priviledge level of the executing code. They have to be masked off to get the address of a faulting instruction. Dave -- J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)