public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jbrejon at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24318] GDB prints the wrong value
Date: Tue, 07 Apr 2020 21:40:01 +0000	[thread overview]
Message-ID: <bug-24318-4717-HWNlq9xhXe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24318-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from e <jbrejon at gmail dot com> ---
(In reply to Hannes Domani from comment #3)
> (In reply to e from comment #2)
> > (In reply to Hannes Domani from comment #1)
> > > (In reply to e from comment #0)
> > > > main.c :
> > > > uint64_t * tab;
> > > > 
> > > > test.c :
> > > > extern uint64_t tab[];
> > > 
> > > This looks like undefined behavior to me.
> > 
> > I believe the C standard is not the issue here.
> > Its about gdb consistency.
> 
> How could there be consistency when tab isn't consistent the same type
> everywhere?

My original post contains two experiments in which the same exact code is
executed. In those experiments GDB does not prints the same values for the same
elements at the same moment.
Same code executed (consistentcy), not the same output (unconsistency).

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

  parent reply	other threads:[~2020-04-07 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24318-4717@http.sourceware.org/bugzilla/>
2020-04-07 19:05 ` ssbssa at sourceware dot org
2020-04-07 20:29 ` jbrejon at gmail dot com
2020-04-07 20:38 ` ssbssa at sourceware dot org
2020-04-07 21:40 ` jbrejon at gmail dot com [this message]
2023-08-03 16:06 ` tromey at sourceware dot org
2023-08-03 17:44 ` jbrejon at gmail 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-24318-4717-HWNlq9xhXe@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: link
Be 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).