Illegal instruction error in some versions of valgrind

Steve Edmonds <[email protected]> Tue, 27 Jan 2026 13:06:51 +1300
Newsgroups gmane.comp.debugging.valgrind
Message-ID <[email protected]> 
This is a multi-part message in MIME format.
--===============0044372922796031124==
Content-Type: multipart/alternative;
 boundary="------------uhLSexcItykhUJrxoLG1s210"
Content-Language: en-GB

This is a multi-part message in MIME format.
--------------uhLSexcItykhUJrxoLG1s210
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi. I have just joined the group to see if I can resolve a long standing 
issue with valgrind on Opensuse.
I have been using some accounting software for many years, initially it 
ran fine and then at some point it started causing a segmentation fault.

I then started using it with valgrind, successful with some versions of 
valgrind and not with others, when it fails I get the following before 
termination and core dump.

==199084==  Illegal opcode at address 0x453BC82
==199084==    at 0x453BC82: write_vec (xcb_conn.c:262)

Using valgrind from the latest Leap 15.6 and 16.0 repositories fails 
(valgrind-3.26.0-355.d_t.2.x86_64.rpm, 3.24.0-150600.3.3.1, 
3.22.0-150600.1.3, 3.24.0-160000.2.2 and 3.25.1-160000.1.1) I do have 
the software running successfully with versions 3.25.1-350.d_t.1 (on 
Leap 15.6) and 3.13.0-lp150.4.61-x86_64 (on Leap 15.0 in a VM). I am 
trying to get to grips with what might determine a successful version of 
valgrind, I can no longer locate the rpm for 3.25.1-350.d_t.1 to try on 
Leap 16.0 and quite happy to build from source if there is some 
configuration in the source that will resolve this issue. Any help much 
appreciated, Steve
--------------uhLSexcItykhUJrxoLG1s210
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Hi. I have just joined the group to see if I can resolve a long
    standing issue with valgrind on Opensuse.<br>
    I have been using some accounting software for many years, initially
    it ran fine and then at some point it started causing a segmentation
    fault.<br>
    <br>
    I then started using it with valgrind, successful with some versions
    of valgrind and not with others, when it fails I get the following
    before termination and core dump.<br>
    <br>
    ==199084==  Illegal opcode at address 0x453BC82<br>
    ==199084==    at 0x453BC82: write_vec (xcb_conn.c:262)<br>
    <br>
    Using valgrind from the latest Leap 15.6 and 16.0 repositories fails
    (valgrind-3.26.0-355.d_t.2.x86_64.rpm, 3.24.0-150600.3.3.1,
    3.22.0-150600.1.3, 3.24.0-160000.2.2 and <span
    style="white-space: pre-wrap">3.25.1-160000.1.1)
I do have the software running successfully with versions 3.25.1-350.d_t.1 (on Leap 15.6) and 3.13.0-lp150.4.61-x86_64 (on Leap 15.0 in a VM).

I am trying to get to grips with what might determine a successful version of valgrind, I can no longer locate the rpm for </span><span
    style="white-space: pre-wrap">3.25.1-350.d_t.1 to try on Leap 16.0 and quite happy to build from source if there is some configuration in the source that will resolve this issue.

Any help much appreciated, Steve
</span>
    <style type="text/css">p, li { white-space: pre-wrap; }hr { height: 1px; border-width: 0; }li.unchecked::marker { content: "\2610"; }li.checked::marker { content: "\2612"; }</style>
  </body>
</html>

--------------uhLSexcItykhUJrxoLG1s210--


--===============0044372922796031124==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============0044372922796031124==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

--===============0044372922796031124==--