[Bug tui/10771] New: Crash when using "layout next" without running process

[Bug tui/10771] New: Crash when using "layout next" without running process

[vz-gdb at zeitlins dot org]

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!

-- 
           Summary: Crash when using "layout next" without running process
           Product: gdb
           Version: 7.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: tui
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: vz-gdb at zeitlins dot org
                CC: gdb-prs at sourceware dot org
  GCC host triplet: x86_64-unknown-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=10771

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug tui/10771] Crash when using "layout next" without running process

[andrewwest at gmail dot com]

------- Additional Comments From andrewwest at gmail dot com  2010-02-27 12:36 -------
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.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrewwest at gmail dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=10771

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug tui/10771] Crash when using "layout next" without running process

[tromey at redhat dot com]

------- Additional Comments From tromey at redhat dot com  2010-03-17 18:29 -------
*** Bug 11392 has been marked as a duplicate of this bug. ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |justin dot lebar+gdb at
                   |                            |gmail dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=10771

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug tui/10771] Crash when using "layout next" without running process

[drow at sources dot redhat dot com]

------- Additional Comments From drow at sources dot redhat dot com  2010-03-22 13:23 -------
Really marking as fixed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED


http://sourceware.org/bugzilla/show_bug.cgi?id=10771

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug tui/10771] Crash when using "layout next" without running process

[drow at sources dot redhat dot com]

------- Additional Comments From drow at sources dot redhat dot com  2010-03-22 13:23 -------
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.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10771

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.