[Bug gdb/15955] New: gdb sometimes shows incorrect values for variables

[Bug gdb/15955] New: gdb sometimes shows incorrect values for variables

[bhuvibhuvanesh at gmail dot com]

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

            Bug ID: 15955
           Summary: gdb sometimes shows incorrect values for variables
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: bhuvibhuvanesh at gmail dot com

Created attachment 7197
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7197&action=edit
demo c code used to showcase the bug. variable which is displayed wrong =
optind

When printing the values for varaiables gdb sometimes shows wrong values.
Not sure under what conditions this occurs, attached the demo c code where this
happens.

gdb always shows the vaule of optind varable as 1, while the printf statement
in the code shows otherwise.

run the code with
(gdb)break main 
(gdb)run -o file1 file2 file3
and step through the code until you reach the for loop
and check the value of optind variable, it shous 1,where it should be 3.
(gdb)print optind


gdb version details:
GNU gdb (GDB) 7.6 (Debian 7.6-5)

gdb configuartion :
x86_64-linux-gnu

Distro used : Debian testing

Can also confirm this is in version 7.5 and also in 32bit version.

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

[Bug gdb/15955] gdb sometimes shows incorrect values for variables

[tromey at redhat dot com]

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

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |tromey at redhat dot com
         Resolution|---                         |DUPLICATE

--- Comment #1 from Tom Tromey <tromey at redhat dot com> ---
Seems to be a dup.

*** This bug has been marked as a duplicate of bug 8588 ***

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