shawn wrote:
>> Any idea what the cause is? E.g., can you find where in the function it
>> crashes by judicious use of printf, do you know what is on line 840 in
>> the source of the binary you are testing, or can you get gdb to print
>> which part of the assembly 0x2c2e0a4c refers to?
>
> Dump of assembler code for function fopen64(char const*, char const*):
> 0x022e09d4 <+0>: push {r4, r5, lr}
[...]
Maybe ASLR has caused a different address to be used here. :(
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
