Re: [Valgrind-users] location of stack allocation printed a at 0x8B43AF0: ??? ...

2019-03-21 Thread Philippe Waroquiers
On Thu, 2019-03-21 at 20:00 +0100, Matthias Apitz wrote: > Hello, > > Why are only the '???' marks printed for the localtion of the stack > allocation? This is with 3.18.0 on Linux x64: 3.18.0 ? Last release is 3.14. > > ==24390== Conditional jump or move depends on uninitialised value(s) > ==24

Re: [Valgrind-users] VEX temporary storage exhausted

2019-03-21 Thread Philippe Waroquiers
On Wed, 2019-03-20 at 23:20 +0100, Yuri D'Elia wrote: > On Wed, Mar 20 2019, Philippe Waroquiers wrote: > > Easiest thing to try initially is to recompile with a bigger size. > > After bumping buffers 10x, I get this: > > ==14645== Memcheck, a memory error detector > ==14645== Copyright (C) 2002-

[Valgrind-users] location of stack allocation printed a at 0x8B43AF0: ??? ...

2019-03-21 Thread Matthias Apitz
Hello, Why are only the '???' marks printed for the localtion of the stack allocation? This is with 3.18.0 on Linux x64: ==24390== Conditional jump or move depends on uninitialised value(s) ==24390==at 0x8B5DC3A: CatTmFilterExclude (CATTmFilter.c:215) ==24390==by 0x8B8069C: SRVCatSearchM