[Bug gdb/25350] gdb internal-error with assertion status failed

[Bug gdb/25350] gdb internal-error with assertion status failed

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=25350

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vries at gcc dot gnu.org

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
If we just disable the assert, we have:
...
$ gdb a.out -ex "break *eh2+0x7e" -ex r 
Reading symbols from a.out...
Breakpoint 1 at 0x4008b1: file small.c, line 38.
Starting program: a.out 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Breakpoint 1, 0x00000000004008b1 in eh2 (p=0x4008b2 <continuation>) at
small.c:38
38      }
(gdb) 
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/25350] gdb internal-error with assertion status failed

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=25350

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
The "break *eh2+0x7e" sets a breakpoint at the last insn of eh2.

We can get that address using:
...
$ address=$(gdb -batch a.out -ex "disassemble eh2" ' \
  | tail -n 2 \
  | head -n 1 \
  | awk '{print $1}')
...
and then use that variable to reproduce without hard-coding an offset:
...
$ gdb -batch a.out -ex "b *$address" -ex r
...

This way, we can also reproduce without -fsanitize=undefined:
...
$ gcc -g small.c
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/25350] gdb internal-error with assertion status failed

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=25350

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> If we just disable the assert, we have:
> ...
> $ gdb a.out -ex "break *eh2+0x7e" -ex r 
> Reading symbols from a.out...
> Breakpoint 1 at 0x4008b1: file small.c, line 38.
> Starting program: a.out 
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> 
> Breakpoint 1, 0x00000000004008b1 in eh2 (p=0x4008b2 <continuation>) at
> small.c:38
> 38      }
> (gdb) 
> ...

Which looks pretty similar to what we get with gdb 7.12.1 (the last release
before gdb 8.0, which introduced the assert):
...
$ gdb a.out -ex "b *$address" -ex r
Reading symbols from a.out...done.
Breakpoint 1 at 0x40070b: file small.c, line 38.
Starting program: /home/vries/gdb_versions/devel/a.out 

Breakpoint 1, 0x000000000040070b in eh2 (p=0x40070c <continuation>) at
small.c:38
38      }
(gdb) 
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/25350] gdb internal-error with assertion status failed

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=25350

--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
Does not reproduce after commit 547ce8f00b "[gdb/backtrace] Fix printing of
fortran string args".

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/25350] gdb internal-error with assertion status failed

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=25350

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f569c1c51a1ff643fc7ba961555fe1067dcf5304

commit f569c1c51a1ff643fc7ba961555fe1067dcf5304
Author: Tom de Vries <tdevries@suse.de>
Date:   Sun Aug 16 13:30:34 2020 +0200

    [gdb/testsuite] Add gdb.base/eh_return.exp

    In PR25350, an internal error was reported:
    ...
    (gdb) break *eh2+0x7e
    Breakpoint 1 at 0x13e2: file small.c, line 38.
    (gdb) run
    Starting program: a.out
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/usr/lib/libthread_db.so.1".

    Breakpoint 1, 0x00005555555553e2 in eh2 (
    frame.c:558: internal-error: frame_id get_frame_id(frame_info*): \
      Assertion `stashed' failed.
    A problem internal to GDB has been detected,
    further debugging may prove unreliable.
    ...

    The internal error does not reproduce after recent commit 547ce8f00b
    "[gdb/backtrace] Fix printing of fortran string args".

    Add the corresponding test-case as regression test, given that the code is
    rather atypical.

    Tested on x86_64-linux.

    gdb/testsuite/ChangeLog:

    2020-08-16  Tom de Vries  <tdevries@suse.de>

            PR gdb/25350
            * gdb.base/eh_return.c: New test.
            * gdb.base/eh_return.exp: New file.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/25350] gdb internal-error with assertion status failed

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=25350

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
   Target Milestone|---                         |10.1
         Resolution|---                         |FIXED

--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
Passing test-case added, marking resolved-fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/25350] gdb internal-error with assertion status failed

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=25350

--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
*** Bug 26364 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.