This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2133842 - TestClientServer_SinglelineStringFormattedWithBigInts from delve internal testsuite fails with SIGILL on rhel-9.2
Summary: TestClientServer_SinglelineStringFormattedWithBigInts from delve internal tes...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: delve
Version: 9.2
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Benoit
QA Contact: Edjunior Barbosa Machado
URL:
Whiteboard:
Depends On:
Blocks: 2137205 2218140
TreeView+ depends on / blocked
 
Reported: 2022-10-11 15:01 UTC by Edjunior Barbosa Machado
Modified: 2023-09-22 16:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2137205 2218140 (view as bug list)
Environment:
Last Closed: 2023-09-22 16:34:01 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7373 0 None Migrated None 2023-09-22 16:33:42 UTC
Red Hat Issue Tracker RHELPLAN-136142 0 None None None 2022-10-11 15:18:54 UTC

Description Edjunior Barbosa Machado 2022-10-11 15:01:44 UTC 
Description of problem:
TestClientServer_SinglelineStringFormattedWithBigInts from delve-1.9.1-1.el9 fails with 'SIGILL: illegal instruction' on RHEL-9.2.0-20221005.0:

(...)
=== RUN   TestClientServer_SinglelineStringFormattedWithBigInts
SIGILL: illegal instruction
PC=0x48268e m=0 sigcode=2
instruction bytes: 0xc5 0xfd 0x73 0xf0 0x24 0xcc 0xfe 0x7f 0x3 0xc3 0x0 0x0 0x0 0x0 0x0 0x0

goroutine 1 [running]:
main.VPSLLQ36(0xc000092ed8, 0xc000092ef8)
	/home/tmp.nwFa0KeaC1/BUILD/delve-1.9.1/_build/src/github.com/go-delve/delve/_fixtures/xmm0print/main.s:7 +0xe fp=0xc000092e98 sp=0xc000092e90 pc=0x48268e
main.main()
	/home/tmp.nwFa0KeaC1/BUILD/delve-1.9.1/_build/src/github.com/go-delve/delve/_fixtures/xmm0print/main.go:11 +0x6e fp=0xc000092f80 sp=0xc000092e98 pc=0x48252e
runtime.main()
	/usr/lib/golang/src/runtime/proc.go:250 +0x212 fp=0xc000092fe0 sp=0xc000092f80 pc=0x433fd2
runtime.goexit()
	/usr/lib/golang/src/runtime/asm_amd64.s:1594 +0x1 fp=0xc000092fe8 sp=0xc000092fe0 pc=0x45cdc1

goroutine 2 [force gc (idle)]:
runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
	/usr/lib/golang/src/runtime/proc.go:363 +0xd6 fp=0xc000042fb0 sp=0xc000042f90 pc=0x434396
runtime.goparkunlock(...)
	/usr/lib/golang/src/runtime/proc.go:369
runtime.forcegchelper()
	/usr/lib/golang/src/runtime/proc.go:302 +0xad fp=0xc000042fe0 sp=0xc000042fb0 pc=0x43422d
runtime.goexit()
	/usr/lib/golang/src/runtime/asm_amd64.s:1594 +0x1 fp=0xc000042fe8 sp=0xc000042fe0 pc=0x45cdc1
created by runtime.init.6
	/usr/lib/golang/src/runtime/proc.go:290 +0x25

goroutine 17 [GC sweep wait]:
runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
	/usr/lib/golang/src/runtime/proc.go:363 +0xd6 fp=0xc00003e790 sp=0xc00003e770 pc=0x434396
runtime.goparkunlock(...)
	/usr/lib/golang/src/runtime/proc.go:369
runtime.bgsweep(0x0?)
	/usr/lib/golang/src/runtime/mgcsweep.go:278 +0x8e fp=0xc00003e7c8 sp=0xc00003e790 pc=0x4214ce
runtime.gcenable.func1()
	/usr/lib/golang/src/runtime/mgc.go:178 +0x26 fp=0xc00003e7e0 sp=0xc00003e7c8 pc=0x416386
runtime.goexit()
	/usr/lib/golang/src/runtime/asm_amd64.s:1594 +0x1 fp=0xc00003e7e8 sp=0xc00003e7e0 pc=0x45cdc1
created by runtime.gcenable
	/usr/lib/golang/src/runtime/mgc.go:178 +0x6b

goroutine 18 [GC scavenge wait]:
runtime.gopark(0xc000080000?, 0x4b8c90?, 0x1?, 0x0?, 0x0?)
	/usr/lib/golang/src/runtime/proc.go:363 +0xd6 fp=0xc00003ef70 sp=0xc00003ef50 pc=0x434396
runtime.goparkunlock(...)
	/usr/lib/golang/src/runtime/proc.go:369
runtime.(*scavengerState).park(0x52b6a0)
	/usr/lib/golang/src/runtime/mgcscavenge.go:389 +0x53 fp=0xc00003efa0 sp=0xc00003ef70 pc=0x41f573
runtime.bgscavenge(0x0?)
	/usr/lib/golang/src/runtime/mgcscavenge.go:617 +0x45 fp=0xc00003efc8 sp=0xc00003efa0 pc=0x41fb45
runtime.gcenable.func2()
	/usr/lib/golang/src/runtime/mgc.go:179 +0x26 fp=0xc00003efe0 sp=0xc00003efc8 pc=0x416326
runtime.goexit()
	/usr/lib/golang/src/runtime/asm_amd64.s:1594 +0x1 fp=0xc00003efe8 sp=0xc00003efe0 pc=0x45cdc1
created by runtime.gcenable
	/usr/lib/golang/src/runtime/mgc.go:179 +0xaa

goroutine 19 [finalizer wait]:
runtime.gopark(0x0?, 0xc000042670?, 0x2b?, 0x38?, 0xc000042770?)
	/usr/lib/golang/src/runtime/proc.go:363 +0xd6 fp=0xc000042628 sp=0xc000042608 pc=0x434396
runtime.goparkunlock(...)
	/usr/lib/golang/src/runtime/proc.go:369
runtime.runfinq()
	/usr/lib/golang/src/runtime/mfinal.go:180 +0x10f fp=0xc0000427e0 sp=0xc000042628 pc=0x41548f
runtime.goexit()
	/usr/lib/golang/src/runtime/asm_amd64.s:1594 +0x1 fp=0xc0000427e8 sp=0xc0000427e0 pc=0x45cdc1
created by runtime.createfing
	/usr/lib/golang/src/runtime/mfinal.go:157 +0x45

rax    0xc000092ed8
rbx    0xc000092ef8
rcx    0x0
rdx    0x4a1be0
rdi    0xc00008c000
rsi    0x1
rbp    0xc000092f70
rsp    0xc000092e90
r8     0x10
r9     0x0
r10    0x7fd576a3cee8
r11    0x4b8c90
r12    0xc000092f18
r13    0x8
r14    0xc0000081a0
r15    0x7fd576ba0111
rip    0x48268e
rflags 0x10202
cs     0x33
fs     0x0
gs     0x0
--- FAIL: TestClientServer_SinglelineStringFormattedWithBigInts (0.66s)
(...)

Version-Release number of selected component (if applicable):
RHEL-9.2.0-20221005.0
delve-1.9.1-1.el9

How reproducible:
100%

Steps to Reproduce:
1. rpm -ivh delve-1.9.1-1.el9.src.rpm
2. rpmbuild -bp rpmbuild/SPECS/delve.spec
3. cd rpmbuild/BUILD/delve-1.9.1/_build/
4. export GO111MODULE=off
5. export GOPATH=$(pwd)
6. go test github.com/go-delve/delve/service/test -count 1 -v
Comment 2 RHEL Program Management 2023-09-22 16:32:10 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3 RHEL Program Management 2023-09-22 16:34:01 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.