-Original Message-
From: Josef Weidendorfer [mailto:josef.weidendor...@gmx.de]
Sent: Monday, June 21, 2010 9:27 AM
To: valgrind-users@lists.sourceforge.net
Cc: Satya V. Gupta
Subject: Re: [Valgrind-users] Running Valgrind on ELF/ python/ boost based
executables
On Thursday 17 June 2010, Satya
-users@lists.sourceforge.net
Cc: Satya V. Gupta
Subject: Re: [Valgrind-users] Running Valgrind on ELF/ python/ boost based
executables
On Wednesday 23 June 2010, Satya V. Gupta wrote:
Josef/ Julian
The problem I have with --demangle=no is that:
a) I am using Python to generate code dynamically
With --demangle=yes, Valgrind generates a SIGSEGV almost immediately in
VG_(strcmp) and with --demangle=no, it doesn't. Pretty symbols would have
helped me get closer to a solution to my problem, but ugly symbols are
not very helpful.
Just to make this very clear: you can convert an ugly
: Wednesday, June 23, 2010 6:46 AM
To: Satya V. Gupta
Cc: valgrind-users@lists.sourceforge.net; 'Josef Weidendorfer'
Subject: Re: [Valgrind-users] Running Valgrind on ELF/ python/ boost based
executables
With --demangle=yes, Valgrind generates a SIGSEGV almost immediately
in
VG_(strcmp
On Jun 23, 2010, at 5:59 AM CDT, Satya V. Gupta wrote:
Would you happen to know if c++filt requires the instrumented process to be
running in order for it to do the translation? Or is the required
information already present in the Valgrind trace for c++filt to do this
translation
] Running Valgrind on ELF/ python/ boost based
executables
On Thursday 17 June 2010, Satya V. Gupta wrote:
Since you asked, I ran Valgrind with --demangle=no; the SIGSEGV issue
I saw earlier went away.
Very good.
However, I had gone to great lengths to insert symbol information into
my image
On Thursday 17 June 2010, Satya V. Gupta wrote:
Since you asked, I ran Valgrind with --demangle=no; the SIGSEGV issue I saw
earlier went away.
Very good.
However, I had gone to great lengths to insert symbol information into my
image in order to chase down a run time issue I am having with
, June 16, 2010 1:56 PM
To: valgrind-users@lists.sourceforge.net
Cc: Satya V. Gupta
Subject: Re: [Valgrind-users] Running Valgrind on ELF/ python/ boost based
executables
On Wednesday 16 June 2010, Satya V. Gupta wrote:
I made the suggested change (bumped up the Stack size to 512 pages
instead
] On Behalf
Of Bart Van Assche
Sent: Sunday, June 13, 2010 6:06 AM
To: Satya V. Gupta
Cc: valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Running Valgrind on ELF/ python/ boost based
executables
On Sun, Jun 13, 2010 at 11:47 AM, Satya V. Gupta guptasa...@netzero.net
wrote:
I have
Bart, Julian
The suggested fix seemed to eliminate the crash.
Thanks
SVG
--Original Message--
From: Bart Van Assche
Sender: bart.vanass...@gmail.com
To: Satya V. Gupta
Cc: valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Running Valgrind on ELF/ python/ boost based
I have a supervisory process that is kicked off by an ELF executable which
in turn invokes some ELF/ python script/ executables based child processes.
I wish to run valgrind with --tool=callgrind and be able to inject valgrind
into all processes. So far I have tried to run the supervisory process
On Sun, Jun 13, 2010 at 11:47 AM, Satya V. Gupta guptasa...@netzero.net wrote:
I have a supervisory process that is kicked off by an ELF executable which
in turn invokes some ELF/ python script/ executables based child processes.
I wish to run valgrind with --tool=callgrind and be able to
12 matches
Mail list logo
