| Summary: | valgrind 3.18.1 crashes on RHEL 6.7 debuginfo Assertion 'in_rx' failed in libmagic.so | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | bug.reporter42 |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | grzegorz.roszak, pjfloyd |
| Priority: | NOR | ||
| Version First Reported In: | 3.18.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Valgrind 3.18.1 crash trachback in debug info on RHEL 6.7 | ||
|
Description
bug.reporter42
2021-11-22 19:56:06 UTC
Which compiler are you using? (In reply to Paul Floyd from comment #1) > Which compiler are you using? (In reply to Paul Floyd from comment #1) > Which compiler are you using? I can confirm the same issue on RHEL6.8 (Santiago) with both code under test and valgrind compiled with GCC 11.1.0. (In reply to Paul Floyd from comment #1) > Which compiler are you using? gcc 4.4.7; however, I also tried using gcc 4.8, 4.9 and 7.4 with the same results. I'll see if I can access a RHEL 6.7 machine. I tried this on a machine Red Hat Enterprise Linux Workstation release 6.7 (Santiago) $ gcc --version gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16) I had difficulty building Valgrind due to as not understanding rdseed (https://bugs.kde.org/show_bug.cgi?id=440502). I made a few changes to hard code out rdseed. The result was no problem running valgrind. (In reply to Paul Floyd from comment #5) > I tried this on a machine > Red Hat Enterprise Linux Workstation release 6.7 (Santiago) > > $ gcc --version > gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16) > > I had difficulty building Valgrind due to as not understanding rdseed > (https://bugs.kde.org/show_bug.cgi?id=440502). I made a few changes to hard > code out rdseed. > > The result was no problem running valgrind. Agreed, I can run valgrind with some binaries just fine, but on a more complicated program that accesses libmagic, I get the failure. A simple test program using libmagic succeeds. (Like the "file" command). I'm not a liberty to provide you with the binary that produces the problem which is why I attached the debug log from valgrind running the problematic program. Is there any further information that I can provide to help track down this issue? We are unable to use the latest version of valgrind due to this problem. Thank you. Again I can't reproduce this with 'file'. git HEAD with this small change
$ git diff
diff --git a/VEX/priv/guest_amd64_helpers.c b/VEX/priv/guest_amd64_helpers.c
index ba71c1b..5269d78 100644
--- a/VEX/priv/guest_amd64_helpers.c
+++ b/VEX/priv/guest_amd64_helpers.c
@@ -3951,7 +3951,7 @@ ULong amd64g_dirtyhelper_RDRAND ( void ) {
}
ULong amd64g_dirtyhelper_RDSEED ( void ) {
-# if defined(__x86_64__)
+# if defined(__x86_64__) && 0
ULong res = 0;
ULong cflag = 0;
__asm__ __volatile__(
$ cat /etc/redhat-release
Red Hat Enterprise Linux Workstation release 6.7 (Santiago)
$ ./vg-in-place -q file ./build.ksh
./build.ksh: Korn shell script text executable
$ ls -al /usr/lib64/libmagic.so.1.0.0
-rwxr-xr-x 1 root root 118112 Aug 4 2014 /usr/lib64/libmagic.so.1.0.0
$ rpm -q --whatprovides /usr/lib64/libmagic.so.1.0.0
file-libs-5.04-21.el6.x86_64
|