public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "marc.dumais at ericsson dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/17373] fast tracepoints with local variables captured - reported as "<unavailable>"
Date: Thu, 11 Sep 2014 14:55:00 -0000	[thread overview]
Message-ID: <bug-17373-4717-v1DfmnbnoY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17373-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Marc Dumais <marc.dumais at ericsson dot com> ---
I have reproduced the issue with gdb 7.2 : with this one the apparent problem
reported is a bit more specific/raw, compared to newer gdb:


(gdb) tfind
Found trace frame 0, tracepoint 3
#0  test (n=10000) at long1.c:9
9            printf("long1: count: %d\n",i);
(gdb) tdump
Data collected at tracepoint 3, trace frame 0:
i = 0
j = {1, 2, 3, 4}
n = 10000
i = 0
j = {1, 2, 3, 4}
(gdb) tfind
Found trace frame 1, tracepoint 2
10            sleep(1);
(gdb) tdump
Data collected at tracepoint 2, trace frame 1:
i = <error reading variable i (Cannot access memory at address 0x7fff5883e87c)>
j = <error reading variable j (Cannot access memory at address 0x7fff5883e860)>
n = <error reading variable n (Cannot access memory at address 0x7fff5883e85c)>
i = Cannot access memory at address 0x7fff5883e87c

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


      parent reply	other threads:[~2014-09-11 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 13:48 [Bug server/17373] New: " marc.dumais at ericsson dot com
2014-09-11 13:49 ` [Bug server/17373] " marc.dumais at ericsson dot com
2014-09-11 13:49 ` marc.dumais at ericsson dot com
2014-09-11 14:45 ` marc.khouzam at ericsson dot com
2014-09-11 14:55 ` marc.dumais at ericsson dot com [this message]

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-17373-4717-v1DfmnbnoY@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).