|
From: TongKe X. <tk...@gr...> - 2008-05-05 00:08:04
|
Hi!
Is it possible,
in my C/C++ code (which compies to a.out)
to call some function foo()
so that when I run: valgrind ./a.out,
whenever execution hits foo()
a backtrace / stack frames are printed out (like the print outs for
invalid read/writes).
Thanks!
--TongKe
|
|
From: Julian S. <js...@ac...> - 2008-05-05 00:13:27
|
On Monday 05 May 2008 02:08, TongKe Xue wrote:
> Hi!
>
> Is it possible,
>
> in my C/C++ code (which compies to a.out)
> to call some function foo()
>
> so that when I run: valgrind ./a.out,
> whenever execution hits foo()
>
> a backtrace / stack frames are printed out (like the print outs for
> invalid read/writes).
#include <valgrind/valgrind.h>
...
VALGRIND_PRINTF_BACKTRACE("The answer is %d\n", 42);
J
|
|
From: TongKe X. <tk...@gr...> - 2008-05-05 02:23:08
|
Being greed here now ... how can I get this returned as a const char* or
have it write it to a buffer I pass it?
(Don't see any obvious way from the implement of
VALGRIND_PRINTF_BACKTRACE).
--TongKe
On Mon, 5 May 2008, Julian Seward wrote:
> On Monday 05 May 2008 02:08, TongKe Xue wrote:
>> Hi!
>>
>> Is it possible,
>>
>> in my C/C++ code (which compies to a.out)
>> to call some function foo()
>>
>> so that when I run: valgrind ./a.out,
>> whenever execution hits foo()
>>
>> a backtrace / stack frames are printed out (like the print outs for
>> invalid read/writes).
>
> #include <valgrind/valgrind.h>
>
> ...
>
> VALGRIND_PRINTF_BACKTRACE("The answer is %d\n", 42);
>
> J
>
|
|
From: Robert W. <rj...@du...> - 2008-05-05 04:00:41
|
There's nothing there to do that right now but it would be fairly easy
to custom hack something to do it.
On May 4, 2008, at 7:23 PM, TongKe Xue wrote:
> Being greed here now ... how can I get this returned as a const
> char* or
> have it write it to a buffer I pass it?
>
> (Don't see any obvious way from the implement of
> VALGRIND_PRINTF_BACKTRACE).
>
> --TongKe
>
> On Mon, 5 May 2008, Julian Seward wrote:
>
>> On Monday 05 May 2008 02:08, TongKe Xue wrote:
>>> Hi!
>>>
>>> Is it possible,
>>>
>>> in my C/C++ code (which compies to a.out)
>>> to call some function foo()
>>>
>>> so that when I run: valgrind ./a.out,
>>> whenever execution hits foo()
>>>
>>> a backtrace / stack frames are printed out (like the print outs
>>> for
>>> invalid read/writes).
>>
>> #include <valgrind/valgrind.h>
>>
>> ...
>>
>> VALGRIND_PRINTF_BACKTRACE("The answer is %d\n", 42);
>>
>> J
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
|
|
From: Venefax <ve...@gm...> - 2008-05-05 04:10:53
|
Dear Julian
Do you remember the bug where the multimedia opcodes were no recognized by
Valgrind? Is there an estimated date for a new version?
Yours
federico
-----Original Message-----
From: val...@li...
[mailto:val...@li...] On Behalf Of Robert
Walsh
Sent: Monday, May 05, 2008 12:01 AM
To: TongKe Xue
Cc: Julian Seward; val...@li...
Subject: Re: [Valgrind-users] Printing stack frames
There's nothing there to do that right now but it would be fairly easy
to custom hack something to do it.
On May 4, 2008, at 7:23 PM, TongKe Xue wrote:
> Being greed here now ... how can I get this returned as a const
> char* or
> have it write it to a buffer I pass it?
>
> (Don't see any obvious way from the implement of
> VALGRIND_PRINTF_BACKTRACE).
>
> --TongKe
>
> On Mon, 5 May 2008, Julian Seward wrote:
>
>> On Monday 05 May 2008 02:08, TongKe Xue wrote:
>>> Hi!
>>>
>>> Is it possible,
>>>
>>> in my C/C++ code (which compies to a.out)
>>> to call some function foo()
>>>
>>> so that when I run: valgrind ./a.out,
>>> whenever execution hits foo()
>>>
>>> a backtrace / stack frames are printed out (like the print outs
>>> for
>>> invalid read/writes).
>>
>> #include <valgrind/valgrind.h>
>>
>> ...
>>
>> VALGRIND_PRINTF_BACKTRACE("The answer is %d\n", 42);
>>
>> J
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save
> $100.
> Use priority code J8TL2D2.
>
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao
ne
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao
ne
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users
|
|
From: Paul W. <pa...@bl...> - 2008-05-06 21:29:13
|
Hi Federico, > Do you remember the bug where the multimedia opcodes were no recognized by > Valgrind? Is there an estimated date for a new version? If you want to make sure the bug doesn't get forgotten, the best thing is to file a bug - http://bugs.kde.org/enter_valgrind_bug.cgi Cheers, -- Paul Some days you are the bug, some days you are the windshield. |