Created attachment 14735 [details]
analysis of the coredump

While I was debugging the pintos kernel for a school assignment, I ran into a GDB crash. Specifically, I ran a macro called dumplist (macro file attached, loaded via gdb -x). This macro prints out all the contents of a janky dynamic list implementation in kernel memory. 


Actual result
---------------

I got a coredump file back, and ran a backtrace + looked around the call stack. It looks like the error has something to do with readline. My log of going through the gdb coredump is attached.


Expected result
---------------

N/A gdb shouldn't crash ever even with stupid macros or stupid data


Environment details
-------------------

OS: archlinux
project code: https://github.com/liamnaddell/CSCC69-Pintos
libc version: core/glibc 2.37-2 [installed]
qemu version: extra/qemu-system-x86 7.2.0-3 [installed]
gdb version: GNU gdb (GDB) 12.1
gdb configuration: 
   configure --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
	     --with-auto-load-dir=$debugdir:$datadir/auto-load
	     --with-auto-load-safe-path=$debugdir:$datadir/auto-load
	     --with-expat
	     --with-gdb-datadir=/usr/share/gdb (relocatable)
	     --with-jit-reader-dir=/usr/lib/gdb (relocatable)
	     --without-libunwind-ia64
	     --with-lzma
	     --without-babeltrace
	     --without-intel-pt
	     --with-mpfr
	     --without-xxhash
	     --with-python=/usr (relocatable)
	     --with-python-libdir=/usr/lib (relocatable)
	     --with-debuginfod
	     --with-guile
	     --enable-source-highlight
	     --with-separate-debug-dir=/usr/lib/debug (relocatable)
	     --with-system-gdbinit=/etc/gdb/gdbinit

gcc version: 12.1