[Bug symtab/30738] New: [gdb/symtab, readnow] different symtab order gives different results

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 30738
           Summary: [gdb/symtab, readnow] different symtab order gives
                    different results
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

[ Previously noted at PR25857 ]

Consider the following test-case:
...
$ cat main.c
int
main ()
{
  return 0;
}
$ cat test.c
static int aaa = 1;
$ cat test2.c
static int aaa = 2;
...

Compiled like this:
...
$ gcc main.c test.c test2.c -g
...

Results with -readnow are different:
...
$ gdb -q -batch a.out -ex "print aaa"
$1 = 1
$ gdb -q -batch -readnow a.out -ex "print aaa"
$1 = 2
...

Readnow expands the symtabs in the (reverse?) order of the debug info, while
selective expansion of symtabs results in a list with expansion order.

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