https://bugs.kde.org/show_bug.cgi?id=422715
Bug ID: 422715
Summary: valgrind 3.16.0 vex: the `impossible' happened:
expr_is_guardable: unhandled expr
Product: valgrind
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: williamba...@hotmail.com
Target Milestone: ---
Created attachment 129177
--> https://bugs.kde.org/attachment.cgi?id=129177&action=edit
log file
SUMMARY
valgrind fails with an internal error:
vex: the `impossible' happened:
expr_is_guardable: unhandled expr
vex storage: T total 993007680 bytes allocated
vex storage: P total 496 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
==71737== at 0x5803FDC7: ??? (in /usr/libexec/valgrind/memcheck-x86-linux)
...
==71737== by 0x580FA469: ??? (in /usr/libexec/valgrind/memcheck-x86-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 71737)
==71737== at 0x83C6036: cnv_double_to_string (in
/u/william/linux-dvl/cpag/cpag)
client stack range: [0xFEC2C000 0xFEC37FFF] client SP: 0xFEC32320
valgrind stack range: [0x883AA000 0x884A9FFF] top usage: 6104 of 1048576
STEPS TO REPRODUCE
1. It happens every time when I run my application.
OBSERVED RESULT
Valgrind aborts with an 'impossible' error.
EXPECTED RESULT
Valgrind does not abort.
SOFTWARE/OS VERSIONS
Fedora 31, kernel 5.6.15-200.fc31.x86_64
It is a 64 bit OS, but my application is 32 bit.
valgrind-3.16.0-1.fc31.i686
ADDITIONAL INFORMATION
I have been using valgrind for years on this application, and it never gave an
'impossible' error before.
Google and searching in bugzilla did not find 'expr_is_guardable', so this
might be a new problem in valgrind 3.16.0.
Is this a known problem?
Should I try to make a small example? (The 'cnv_double_to_string' function just
calls sprintf and hasn't been touched for years.)
Should I try to do a bisection on valgrind?
--
You are receiving this mail because:
You are watching all bug changes.
