On 12/09/2019 14:00, Eliot Moss wrote:
On 9/12/2019 5:45 AM, Pallavi Shinde wrote:
We ran valgrind on ndmp by inserting the valgrind command within
/etc/init.d/ndmpd, the script that starts ndmpd.
valgrind did indeed run on ndmpd and we did get a memory check report,
but it didn't keep itsel
On 9/12/2019 5:45 AM, Pallavi Shinde wrote:
We ran valgrind on ndmp by inserting the valgrind command within /etc/init.d/ndmpd, the script that
starts ndmpd.
valgrind did indeed run on ndmpd and we did get a memory check report, but it didn't keep itself
attached to ndmpd. valgrind dumps the
Hi,
Thank you for your comments.
We ran valgrind on ndmp by inserting the valgrind command within
/etc/init.d/ndmpd, the script that starts ndmpd.
valgrind did indeed run on ndmpd and we did get a memory check report, but
it didn't keep itself attached to ndmpd. valgrind dumps the memory c
Probably not unless there happens to be somebody here
that is familiar with "ndmpd" and how it starts up.
You need to make sure that valgrind manages to wind
up running the actual daemon so if there is some kind
of launcher process that starts it then you need to
try and avoid that and start the
Hi,
Can we get any help here ?
Thanks,
Pallavi
On Thu, Sep 5, 2019, 4:28 PM Pallavi Shinde wrote:
> Hi,
>
> Comments prefixed with [PS] below.
>
> > 1. service ndmpd stop
> > 2. service ndmpd start
> > 3. valgrind -v --num-callers=50 --log-file=ndmp_valgrind_30_8.log
> --leak-c
Hi,
Comments prefixed with [PS] below.
> 1. service ndmpd stop
> 2. service ndmpd start
> 3. valgrind -v --num-callers=50 --log-file=ndmp_valgrind_30_8.log
--leak-check=full /usr/local/ndmp/ndmpd
>
> echo $? Returns 1 after the 3rd command.
Does running ndmpd "by hand" work as t
1. service ndmpd stop
2. service ndmpd start
3. valgrind -v --num-callers=50 --log-file=ndmp_valgrind_30_8.log
--leak-check=full /usr/local/ndmp/ndmpd
echo $? Returns 1 after the 3rd command.
Does running ndmpd "by hand" work as the third step?
3. /usr/local/ndmp/ndmpd & # s
