examining Linux core file?

[Chuck Tuffli]

On Tue, Jan 16, 2018 at 5:30 PM, O'Connor, Daniel <darius at dons.net.au> wrote:
>
>
>> On 16 Jan 2018, at 20:29, Konstantin Belousov <kostikbel at gmail.com> wrote:
>>>
>>> My memory is sketchy but you may need to build a complete
>>> cross-toolchain for that. Long-long ago we actually did that but the
>>> resulting linux binaries were weird and needed branding always.
>>
>> No cross-toolchain will help there.  Problem is that the binary is Linux,
>> while core is FreeBSD.  There are enough details significant to the debugger
>> that make such combination a new platform.
>
> 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?

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"

--chuck