public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "markus.t.metzger at intel dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/30073] [intel Efficient-core] FAIL: gdb.btrace/exception.exp: flat (pattern 1)
Date: Thu, 16 Feb 2023 14:52:27 +0000	[thread overview]
Message-ID: <bug-30073-4717-tVLQEovNpy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30073-4717@http.sourceware.org/bugzilla/>

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

--- Comment #9 from Markus Metzger <markus.t.metzger at intel dot com> ---
(In reply to Tom de Vries from comment #8)
> (In reply to Markus Metzger from comment #7)
> > (In reply to Tom de Vries from comment #6)
> > 
> > > record btrace
> > > continue
> > > maint btrace packet-history 0, +100
> > > #record function-call-history 1
> > > #record function-call-history /c 1
> > 
> > The maintenance command doesn't fetch the trace itself.  We'd need some
> > other record command before it, e.g. 'info record' or one of the two
> > commented-out commands.
> 
> With the two commented out commands added back, I have:
> ...
> +continue
> 
> Breakpoint 3, main () at
> /data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc:59
> 59        return ret; /* bp.2  */
> +record function-call-history 1
> 1       main()
> +record function-call-history /c 1
> 1       main()
> +maint btrace packet-history 0, +100
> 0       begin: 0x40076d, end: 0x400779
> ...

Thanks.  Looks like you're not getting any BTS records, either.  The one entry
is the artificial record GDB adds to reach the current PC.

It looks like a kernel issue to me.  I'm discussing it with Intel kernel
developers.  This might take a bit of time.

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

  parent reply	other threads:[~2023-02-16 14:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03  9:26 [Bug record/30073] New: " vries at gcc dot gnu.org
2023-02-03  9:26 ` [Bug record/30073] " vries at gcc dot gnu.org
2023-02-03  9:28 ` vries at gcc dot gnu.org
2023-02-06 12:30 ` vries at gcc dot gnu.org
2023-02-13 18:10 ` vries at gcc dot gnu.org
2023-02-14 11:01 ` vries at gcc dot gnu.org
2023-02-16 11:16 ` markus.t.metzger at intel dot com
2023-02-16 13:32 ` vries at gcc dot gnu.org
2023-02-16 13:54 ` markus.t.metzger at intel dot com
2023-02-16 14:28 ` vries at gcc dot gnu.org
2023-02-16 14:52 ` markus.t.metzger at intel dot com [this message]
2023-02-16 16:00 ` vries at gcc dot gnu.org

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-30073-4717-tVLQEovNpy@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).