[Bug symtab/25067] New: GDB internal error while testing gdb.base/label.exp with -flto

kevinb at redhat dot com sourceware-bugzilla@sourceware.org
Sun Oct 6 05:11:00 GMT 2019


            Bug ID: 25067
           Summary: GDB internal error while testing gdb.base/label.exp
                    with -flto
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: kevinb at redhat dot com
  Target Milestone: ---

Using the installed gcc (gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1)) on Fedora
30, while testing gdb.base/label.exp with -flto, an internal error occurs
within GDB when attempting to set a breakpoint.

The command used to run the test is as follows:

make check RUNTESTFLAGS="CFLAGS_FOR_TARGET='-flto' --target_board unix

Here are the relevant lines from the log file showing the assertion failure:

(gdb) break here
internal-error: void decode_line_full(const event_location*, int,
program_space*, symtab*, int, linespec_result*, const char*, const char*):
Assertion `result.size () == 1 || canonical->pre_expanded' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) FAIL: gdb.base/label.exp: breakpoint here
(GDB internal error)
Resyncing due to internal error.

Here's a partial backtrace...

(top-gdb) bt
#0  internal_error (
    fmt=0x838093 "%s: Assertion `%s' failed.")
#1  0x00000000005c287d in decode_line_full (location=location@entry=0xdd78f0, 
    flags=flags@entry=1, search_pspace=search_pspace@entry=0x0, 
    default_symtab=<optimized out>, default_line=<optimized out>, 
    canonical=0x7fffffffd060, select_mode=0x0, filter=<optimized out>)
#2  0x0000000000489853 in parse_breakpoint_sals (location=0xdd78f0, 
#3  0x0000000000486716 in create_breakpoint (gdbarch=0xdfb8a0, 
    location=0xdd78f0, cond_string=0x0, thread=<optimized out>, 
    extra_string=0x0, parse_extra=1, tempflag=0, type_wanted=bp_breakpoint, 
    ignore_count=0, pending_break_support=AUTO_BOOLEAN_AUTO, 
    ops=0xb7c1c0 <bkpt_breakpoint_ops>, from_tty=1, enabled=1, internal=0, 
#4  0x0000000000486ba1 in break_command_1 (arg=<optimized out>, 
    flag=<optimized out>, from_tty=1)

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

More information about the Gdb-prs mailing list