public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/30073] New: [intel Efficient-core] FAIL: gdb.btrace/exception.exp: flat (pattern 1)
Date: Fri, 03 Feb 2023 09:26:09 +0000	[thread overview]
Message-ID: <bug-30073-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30073
           Summary: [intel Efficient-core] FAIL: gdb.btrace/exception.exp:
                    flat (pattern 1)
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: record
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I got a new laptop, build gdb and ran the gdb testsuite, and ran into:
...
(gdb) PASS: gdb.btrace/exception.exp: continue to breakpoint: cont to bp.2
gdb_expect_list pattern: /1     main\(\)^M
2       test\(\)^M
3       foo\(\)^M
4       bar\(\)^M
5       bad\(\)^M/
record function-call-history 1^M
1       main()^M
(gdb) FAIL: gdb.btrace/exception.exp: flat (pattern 1)
...

I could reproduce it sometimes, but not all the time, till I tried out using
taskset.

When using:
- taskset -c 0-3, the test-case passes.  
- taskset -c 4-11, the test-case fails.

The processor is a i7-1250U with 12 threads:
- 2 performance cores (I guess providing 2 threads per core), and
- 8 efficient cores.

So, I guess somehow it doesn't run properly on efficient cores.

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

             reply	other threads:[~2023-02-03  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03  9:26 vries at gcc dot gnu.org [this message]
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
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@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).