This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug varobj/18564] New: regression in showing __thread so extern variable


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

            Bug ID: 18564
           Summary: regression in showing __thread so extern variable
           Product: gdb
           Version: 7.9
            Status: NEW
          Severity: normal
          Priority: P2
         Component: varobj
          Assignee: unassigned at sourceware dot org
          Reporter: philippe.waroquiers at skynet dot be
  Target Milestone: ---

Created attachment 8378
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8378&action=edit
reproduces bug showing __thread int so_extern   defined in a .so

Between gdb 7.7 and gdb 7.8/7.9, a regression appeared in the display
of __thread variables defined in a shared object.
(I think it regressed in 7.8, bug is still present in 7.9).

To reproduce:
# untar the attachment
tar xf soextern.tar
# compile and link:
./comp
# and reproduce:
gdb ./gtls
break 9
run
p &so_extern
# here the program has printed:
address is 0xb7df3b3c
# while gdb prints:
$1 = (int *) 0x6fdcbb3c
#same problem for the second thread
address is 0xb75f2b3c
$2 = (int *) 0x6f5cab3c
# if you try to print the variable, it fails.
(gdb) p so_extern
Cannot access memory at address 0x6f5cab3c

This is working with gdb 7.7 on Debian 8, x86,
compared with gdb 7.9.1 self compiled, which fails.
Note that this was first detected on various Valgrind buildbots,
where the regression test gdbserver/hgtls started to fail
with gdb versions >= 7.8, but I have not tested myself with 7.8

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]