[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 385707] memcheck-amd64-linux crashing
From:       Daniel Gutson <bugzilla_noreply () kde ! org>
Date:       2018-07-28 22:14:19
Message-ID: bug-385707-17878-WtOLc3aIlR () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=385707

Daniel Gutson <danielgutson@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
         Resolution|INVALID                     |---
             Status|RESOLVED                    |REOPENED

--- Comment #3 from Daniel Gutson <danielgutson@gmail.com> ---
Have you seen this?

--11098-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exiting
--11098-- si_code=128;  Faulting address: 0x0;  sp: 0x802db5dc0

valgrind: the 'impossible' happened:
   Killed by fatal signal


And the program happens to be the python interpreter.
If it is the interpreter doing invalid writes, why valgrind says internal error
and that impossible happened? Shouldn't it be prepared to handle signals?

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]