[Bug symtab/25857] New: Partial symtab expansion state influences lookup results

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

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

            Bug ID: 25857
           Summary: Partial symtab expansion state influences lookup
                    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: ---

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
...

When doing a contextless print of aaa, we get:
...
$ gdb -batch a.out -ex "print aaa"
$1 = 2
...
Same with -readnow.

But when we first expand the psymtab for test.c, we get instead:
...
$ gdb -batch a.out -ex "maint expand-symtab test.c" -ex "print aaa"
$1 = 1
...

This is due to lookup_symbol_in_objfile:
...
/* Perform the standard symbol lookup of NAME in OBJFILE:                       
   1) First search expanded symtabs, and if not found                           
   2) Search the "quick" symtabs (partial or .gdb_index).                       
   BLOCK_INDEX is one of GLOBAL_BLOCK or STATIC_BLOCK.  */
...

I think it's a bug if presence of partial symtabs and expansion state has
influence on the results of gdb.

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