examining Linux core file?

[O'Connor, Daniel]

> On 24 Jan 2018, at 11:15, Chuck Tuffli <chuck at tuffli.net> wrote:
>> 
>> Using ktrace / linux_kdump might help - or at least give some clues as to where it's failing too.
> 
> The ktrace output is interesting. Is there any way to show the address
> causing the segfault?

Not AFAIK, because ktrace only knows about syscalls :(

> dmesg shows:
> pid 1123 (apt-get), uid 0: exited on signal 11 (core dumped)
> 
> ktrace shows:
> ...
>  1123 apt-get  1516724569.278210 CALL  L64  write(0x1,0x800644000,0x21)
>  1123 apt-get  1516724569.284901 GIO   L64  fd 1 wrote 33 bytes
>       "\rBuilding dependency tree... 50%\r"
>  1123 apt-get  1516724569.291711 RET   L64  write 33/0x21
>  1123 apt-get  1516724569.298353 CALL  L64  gettimeofday(0x7fffffffd410,0)
>  1123 apt-get  1516724569.305308 RET   L64  gettimeofday 0
>  1123 apt-get  1516724569.312174 PSIG  L64  SIGSEGV SIG_DFL code=SEGV_MAPERR
>  1123 apt-get  1516724569.312183 NAMI  L64  "apt-get.core"

Looks pretty innocent.. :-/

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C