On Thu, Jul 30, 2015 at 08:52:33PM +0200, Marc Lehmann wrote: > On Tue, Jul 28, 2015 at 11:26:50PM +0200, Kurt Roeckx <[email protected]> wrote: > > > but apart from lzf compression (which does access uninitialised data), > > > there is no output from valgrind either, so it's at leats not some obvious > > > corruption bug. > > > > You could always try something as address santizer. > > Forgive my ignorance, but I have no clue what you are even trying to tell > me - what something should I try as address sanitizer(?), and to what end? > Are you maybe suggetsing I should use e.g. gcc's -fsanitize=address? Or > something else?
Yes, I was talking about -fsanitize=address. I suggest you make a static version of libcrypto/libssl and link that in gvpe. I suggest you build both openssl and gvpe with that option. I currently have no other idea of what the cause could be. Kurt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
