On 05/17/2014 05:24 PM, Toralf Förster wrote:
> On 05/03/2014 09:15 PM, Richard Weinberger wrote:
>> On Sat, May 3, 2014 at 6:04 PM, Toralf Förster
>> wrote:
>>> I could force a crash using latest kernel tree (v3.15-rc3-159-g6c6ca9c with
>>> applied fix3.patch for the mremap syscall) and latest
On 05/03/2014 09:15 PM, Richard Weinberger wrote:
> On Sat, May 3, 2014 at 6:04 PM, Toralf Förster wrote:
>> I could force a crash using latest kernel tree (v3.15-rc3-159-g6c6ca9c with
>> applied fix3.patch for the mremap syscall) and latest trinity tree
>> (1.1-1349-g18ebf71).
...
>> #9 0x080c
On Sat, May 3, 2014 at 6:04 PM, Toralf Förster wrote:
> I could force a crash using latest kernel tree (v3.15-rc3-159-g6c6ca9c with
> applied fix3.patch for the mremap syscall) and latest trinity tree
> (1.1-1349-g18ebf71).
>
> The backtrace of the core dump gives :
>
> tfoerste@n22 ~/tmp $ gdb
I could force a crash using latest kernel tree (v3.15-rc3-159-g6c6ca9c with
applied fix3.patch for the mremap syscall) and latest trinity tree
(1.1-1349-g18ebf71).
The backtrace of the core dump gives :
tfoerste@n22 ~/tmp $ gdb /home/tfoerste/devel/linux/linux
--core=/mnt/ramdisk/core -batch -
