[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 John Baldwin changed: What|Removed |Added Resolution|--- |FIXED Status|Open

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #19 from Leandro Lupori --- (In reply to Mark Millard from comment #18) > GNU gdb (GDB) 8.3.1 [GDB v8.3.1 for FreeBSD] got: > > inferior.c:287: internal-error: struct inferior *find_inferior_pid(int): > Assertion `pid != 0'

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #18 from Mark Millard --- (In reply to Leandro Lupori from comment #17) I tried a 2-socket PowerMac G4 (head -r358510) and, for a minidump, after reboot . . . GNU gdb (GDB) 8.3.1 [GDB v8.3.1 for FreeBSD] got: inferior.c:287:

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #17 from Leandro Lupori --- I've tested dumping and inspecting the crashdump using r358813, on a POWER8 VM. It worked fine. These were the test commands and output: # sysctl debug.kdb.panic=1 ... db> dump Dumping 216 out of

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #16 from Mark Millard --- Head -352175 added ET_DYN to _kvm_probe_elf_kernel and ET_DYN is what started this. As stands dump hangs on the old PowerMac G5s. So I'm unable to produce such powerpc64 dumps to see what the libkvm

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #14 from Mark Millard --- (In reply to John Baldwin from comment #8) With the following hacks I've been able to get an output for the debug.minidump=0 based vmcore.2 (2 GiBYte RAM dumped) for powerpc

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #13 from Mark Millard --- (In reply to Mark Millard from comment #12) I found the "Raw core file not supported" logic in /usr/src/lib/libkvm/kvm_powerpc.c : static int

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #12 from Mark Millard --- (In reply to Mark Millard from comment #11) So trying: ps -M /var/crash/vmcore.2 -N /usr/lib/debug/boot/kernel/kernel.debug for a vmcore.2 based on: debug.minidump=0 things do

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #11 from Mark Millard --- (In reply to Mark Millard from comment #9) [This note is limited to contexts with gcc 4.2.1 based kernels.] Summary after avoiding a user error: looks like there is a default of

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #10 from Mark Millard --- (In reply to John Baldwin from comment #8) The bt that I included shows libstdc++ in use inside /usr/local/bin/gdb, not libc++ . This is because /usr/local/bin/gdb was built under

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #9 from Mark Millard --- (In reply to John Baldwin from comment #5) As for ps -M /var/crash/vmcore.7 listing no processes: main uses kvm_getprocs, which in turn eventually does:

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #8 from John Baldwin --- Can you pop up to frame 13 (solib_svr4_r_map) and 'p *info' and 'p *lmo'? The lack of working exceptions from clang (which appears to be the source of the coredump in gdb itself)

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #7 from Mark Millard --- (In reply to John Baldwin from comment #5) This note is for the /usr/local/bin/gdb crash. As for building ports with debug information, I use as a default context: # svnlite diff

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #6 from Mark Millard --- (In reply to John Baldwin from comment #5) I've used both gdb's as well but I've had more occasions when system's gdb worked and ports did not than the other way around (when there

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #5 from John Baldwin --- I would start with trying to debug why 'ps -M' doesn't work by stepping through 'ps'. In terms of gdb7 vs gdb6, I definitely used gdb7 on userland binaries with threads, fork

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #4 from Mark Millard --- A not as libkvm tied note about which gdb works better for 32-bit powerpc in at least some contexts: I took an a.out (from clang++ targeting powerpc) and tried /usr/local/bin/gdb

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #3 from Mark Millard --- (In reply to Mark Millard from comment #2) An FYI based on my ET_DYN test hack in libkvm: I've gotten some more panics with the libkvm change in place. This makes the new

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 --- Comment #2 from Mark Millard --- (In reply to John Baldwin from comment #1) The ps -M result for using: # svnlite diff /usr/src/lib Index: /usr/src/lib/libkvm/kvm_private.c

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 John Baldwin changed: What|Removed |Added CC||j...@freebsd.org

[Bug 219153] head, stable/11, release/11.0.1: libkvm (& more?) not updated to handle powerpc/powerpc64 ET_DYN based vmcore.* 's and such

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org