public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "bhuvibhuvanesh at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/15955] New: gdb sometimes shows incorrect values for variables Date: Sat, 14 Sep 2013 06:25:00 -0000 [thread overview] Message-ID: <bug-15955-4717@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2013-09-14 6:25 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-14 6:25 bhuvibhuvanesh at gmail dot com [this message] 2013-09-16 15:40 ` [Bug gdb/15955] " tromey at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15955-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).