On 02/20/2018 02:08 PM, Nicolas Sauvaget wrote:
Tomas,
Timers, threads ,"real time behaviour" of your application and GDB
may jostle each other, so you may not be able to use it.
Understood. Luckily, Postgres is single-threaded, and it does not use
timers or realtime stuff, so that should no
code using
VALGRIND_PRINTF_BACKTRACE(). Of course nothing is automatic.
Hope it helps you in your investigations.
Nicolas.
En date de : Mar 20.2.18, Tomas Vondra a écrit :
Objet: Re: [Valgrind-users] how to generate core file on invalid reads/writes?
À: &q
And yes, this
means you are allowed to [you must] watch and help.
I don't follow. Watch and help with what?
It means that scripting the interaction can be quirky, tedious,
and frustrating. Especially the first time, you are likely
to get better results by first invoking everything "by hand",
On 02/19/2018 11:14 PM, John Reiser wrote:
Is there a way to get core when valgrind on invalid access? Am I
missing something?
If you are running valgrind interactively and valgrind reports an error,
then one of the error options is to invoke gdb. Gdb has a command:
generate-core-file
S
Is there a way to get core when valgrind on invalid access? Am I missing
something?
If you are running valgrind interactively and valgrind reports an error,
then one of the error options is to invoke gdb. Gdb has a command:
generate-core-file
See the gdb manual which is available online in
Hi,
I wonder if it's possible to generate cores (or rather vgcores) when
valgrind detects invalid reads or writes. We do occasionally see such
reports by valgrind, and it would be really helpful to be able to
investigate the internal state using gdb. But I don't see any such
option in valgrin
