public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/27791] hw_breakpoint.exp fails to build
Date: Tue, 03 Oct 2023 19:48:07 +0000	[thread overview]
Message-ID: <bug-27791-6586-wvZEUxtdfs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27791-6586@http.sourceware.org/bugzilla/>

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

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wcohen at redhat dot com
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
With the current git checkout of systemtap (commit ca71442b9) see this working
on Fedora rawhide:

Test run by root on Tue Oct  3 15:46:59 2023
Native configuration is x86_64-pc-linux-gnu

                === systemtap tests ===

Schedule of variations:
    unix

Running target unix

Host: Linux rawhide 6.6.0-0.rc3.20230929git9ed22ae6be81.30.fc40.x86_64 #1 SMP
PR
EEMPT_DYNAMIC Fri Sep 29 16:20:55 UTC 2023 x86_64 GNU/Linux
Snapshot: version 5.0/0.189, release-4.8-147-gca71442b
GCC: 13.2.1 [gcc (GCC) 13.2.1 20230918 (Red Hat 13.2.1-3)]
Distro: Fedora release 40 (Rawhide)
SElinux: Enforcing
CPUFlags: flags         : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
m
ca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm
cons
tant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_freq pni
pclmulqdq
 vmx ssse3 fma cx16 pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
tsc_deadline_tim
er aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault
ss
bd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad
fsgsbas
e tsc_adjust sgx bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap
clflushopt
 xsaveopt xsavec xgetbv1 xsaves arat vnmi umip sgx_lc md_clear
arch_capabilities
vmx flags       : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb
flexpr
iority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest shadow_vmcs pml
Lockdown: [none] integrity confidentiality


Running
/home/wcohen/systemtap_write/systemtap/testsuite/systemtap.base/hw_break
point.exp ...
PASS: hw_breakpoint (built and installed module)
PASS: hw_breakpoint (found symbol address)
PASS: hw_breakpoint (found cmd file - /proc/stap_hwbkpt_cmd)
PASS: hw_breakpoint - addr (hw breakpoint support)
PASS: hw_breakpoint - symbol (hw breakpoint support)

                === systemtap Summary ===

# of expected passes            5
/home/wcohen/systemtap_write/install/bin/stap version 5.0/0.189,
release-4.8-147
-gca71442b

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2023-10-03 19:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 14:52 [Bug testsuite/27791] New: " scox at redhat dot com
2021-09-23 13:04 ` [Bug testsuite/27791] " dichen at redhat dot com
2022-05-26 17:42 ` scox at redhat dot com
2023-10-03 19:48 ` wcohen at redhat 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-27791-6586-wvZEUxtdfs@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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).