Date: Wed, 24 Jan 2018 13:19:51 +1030 From: "O'Connor, Daniel" <darius@dons.net.au> To: Chuck Tuffli <chuck@tuffli.net> Cc: Konstantin Belousov <kostikbel@gmail.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, Pedro Giffuni <pfg@freebsd.org> Subject: Re: examining Linux core file? Message-ID: <8ECC1C72-58D3-46D2-B577-22123C7A81DB@dons.net.au> In-Reply-To: <CAM0tzX0pa0H6ghWVerM5ZNF4fZpOHdXNA=M%2BXvrYXZedP%2BZCfQ@mail.gmail.com> References: <bfe13557-55f1-a04a-1367-9cbb58075323@FreeBSD.org> <20180116095908.GQ1684@kib.kiev.ua> <32C3FADA-073C-4942-B12F-AEB7F345766E@dons.net.au> <CAM0tzX0pa0H6ghWVerM5ZNF4fZpOHdXNA=M%2BXvrYXZedP%2BZCfQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 24 Jan 2018, at 11:15, Chuck Tuffli <chuck@tuffli.net> wrote: >>=20 >> Using ktrace / linux_kdump might help - or at least give some clues = as to where it's failing too. >=20 > 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) >=20 > 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=3DSEGV_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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8ECC1C72-58D3-46D2-B577-22123C7A81DB>