Using gdb 7.0-debian (from unstable) I stumbled upon the following bug: if you run "gdb -tui any-program-with-debug-info" and immediately enter "layout next" in the gdb window it crashes with: (gdb) layout next /tmp/buildd/gdb-7.0/gdb/gdbarch.c:1428: internal-error: gdbarch_addr_bit: Assertion `gdbarch != NULL' failed. This is, of course, easy to work around (layout works fine when running the program) but should probably be easy to fix as well so I wanted to report it in case it can be useful. Please let me know if you have any trouble reproducing this and I'll try to provide more information. Thanks!
I'm seeing this as well in the latest Ubuntu, which I believe uses the same package as debian. Steps to reproduce; 1) Compile simple program ( debugging info isn't necessary ), e.g.; echo -e "#include <stdio.h>\nint main( int argc, char** argv )\n{\nprintf( \"testing\\\n\" );\n};" | g++ -xc++ -o testing - 2) Run gdb with the resulting program. gdb ./testing 3) Switch TUI layout layout split Result: /build/buildd/gdb-7.0/gdb/gdbarch.c:1428: internal-error: gdbarch_addr_bit: Assertion `gdbarch != NULL' failed. A problem internal to GDB has been detected, I tried with yesterdays cvs snapshot and this produced the same results.
*** Bug 11392 has been marked as a duplicate of this bug. ***
This will be fixed in GDB 7.2: 2010-03-20 Daniel Jacobowitz <dan@codesourcery.com> * tui/tui-disasm.c (tui_get_begin_asm_address): Default to get_current_arch. * tui/tui-layout.c (extract_display_start_addr): Likewise. It's also fixed in the Debian packages of GDB 7.1.
Really marking as fixed.