|
From: Richard L. <rl...@pe...> - 2008-08-01 15:29:50
|
I'm running valgrind on a dev/QA box for code profiling.
Said box is maintained by IT.
I am not root, cannot get root, and will never ever ever have a chance of being root on hardware of this price tag. :-)
And that's the way it SHOULD be.
But I need to profile my application code.
So I do this:
SERVER DESKTOP
sudo /etc/init.d/httpd stop
sudo valgrind --tool=callgrind /usr/bin/httpd -X
ab -n 10000 -c 1000 http://localhost/my_app
^C
sudo /etc/init.d/httpd start
And valgrind can't write its own output file, because it's root-owned.
I'd LOVE a --output-file=/path/to/some/file which would just use that file, and not attempt to chown/chmod it in any way.
There's a way to get the verbose meta-output elsewhere, but not the actual results, afaics.
Thanks!
PS
I think they'll give me 'sudo chmod /data/home/rlynch/callgrind.out.*' eventually, but I'm sure others would find the ability to control their output useful as well.
--
Richard Lynch
_______________________________________________________
The information in this email or in any file attached
hereto is intended only for the personal and confiden-
tial use of the individual or entity to which it is
addressed and may contain information that is propri-
etary and confidential. If you are not the intended
recipient of this message you are hereby notified that
any review, dissemination, distribution or copying of
this message is strictly prohibited. This communica-
tion is for information purposes only and should not
be regarded as an offer to sell or as a solicitation
of an offer to buy any financial product. Email trans-
mission cannot be guaranteed to be secure or error-
free. P6070214
|
|
From: Julian S. <js...@ac...> - 2008-08-01 15:37:23
|
Doesn't this work?
user options for Callgrind:
dump creation options:
--callgrind-out-file=<f> Output file name [callgrind.out.%p]
J
On Friday 01 August 2008 17:29, Richard Lynch wrote:
> I'm running valgrind on a dev/QA box for code profiling.
>
> Said box is maintained by IT.
>
> I am not root, cannot get root, and will never ever ever have a chance of being root on hardware of this price tag. :-)
>
> And that's the way it SHOULD be.
>
> But I need to profile my application code.
>
> So I do this:
> SERVER DESKTOP
> sudo /etc/init.d/httpd stop
> sudo valgrind --tool=callgrind /usr/bin/httpd -X
> ab -n 10000 -c 1000 http://localhost/my_app
> ^C
> sudo /etc/init.d/httpd start
>
> And valgrind can't write its own output file, because it's root-owned.
>
> I'd LOVE a --output-file=/path/to/some/file which would just use that file, and not attempt to chown/chmod it in any way.
>
> There's a way to get the verbose meta-output elsewhere, but not the actual results, afaics.
>
> Thanks!
>
> PS
> I think they'll give me 'sudo chmod /data/home/rlynch/callgrind.out.*' eventually, but I'm sure others would find the ability to control their output useful as well.
>
> --
> Richard Lynch
>
>
>
> _______________________________________________________
>
> The information in this email or in any file attached
> hereto is intended only for the personal and confiden-
> tial use of the individual or entity to which it is
> addressed and may contain information that is propri-
> etary and confidential. If you are not the intended
> recipient of this message you are hereby notified that
> any review, dissemination, distribution or copying of
> this message is strictly prohibited. This communica-
> tion is for information purposes only and should not
> be regarded as an offer to sell or as a solicitation
> of an offer to buy any financial product. Email trans-
> mission cannot be guaranteed to be secure or error-
> free. P6070214
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
|
|
From: Ashley P. <api...@co...> - 2008-08-01 15:39:19
|
On Fri, 2008-08-01 at 10:29 -0500, Richard Lynch wrote:
> I'm running valgrind on a dev/QA box for code profiling.
>
> Said box is maintained by IT.
>
> I am not root, cannot get root, and will never ever ever have a chance
> of being root on hardware of this price tag. :-)
>
> And that's the way it SHOULD be.
I could argue that if you need a tool to do your job it's ITs role to
ensure you have access to those tools.
> I'd LOVE a --output-file=/path/to/some/file which would just use that file, and not attempt to chown/chmod it in any way.
from "valgrind --tool=callgrind -- help"
--callgrind-out-file=<f> Output file name [callgrind.out.%p]
Does this do what you want? Perhaps you'll could create a empty file in
that name as a normal user and then have valgrind write to it as root.
Ashley,
|
|
From: Richard L. <rl...@pe...> - 2008-08-01 16:56:51
|
My version of valgrind/callgrind (3.2.1) does not list any such argument.
What version are you using?
PS
If it *were* there in my version, I certainly would not have been posting to the list :-)
PPS
IT is going to give that access needed; I just thought it would be handy for other use cases as well.
-----Original Message-----
From: Ashley Pittman [mailto:api...@co...]
Sent: Friday, August 01, 2008 10:39 AM
To: Richard Lynch
Cc: 'val...@li...'
Subject: Re: [Valgrind-users] valgrind output file inaccessible
On Fri, 2008-08-01 at 10:29 -0500, Richard Lynch wrote:
> I'm running valgrind on a dev/QA box for code profiling.
>
> Said box is maintained by IT.
>
> I am not root, cannot get root, and will never ever ever have a chance
> of being root on hardware of this price tag. :-)
>
> And that's the way it SHOULD be.
I could argue that if you need a tool to do your job it's ITs role to
ensure you have access to those tools.
> I'd LOVE a --output-file=/path/to/some/file which would just use that file, and not attempt to chown/chmod it in any way.
from "valgrind --tool=callgrind -- help"
--callgrind-out-file=<f> Output file name [callgrind.out.%p]
Does this do what you want? Perhaps you'll could create a empty file in
that name as a normal user and then have valgrind write to it as root.
Ashley,
_______________________________________________________
The information in this email or in any file attached
hereto is intended only for the personal and confiden-
tial use of the individual or entity to which it is
addressed and may contain information that is propri-
etary and confidential. If you are not the intended
recipient of this message you are hereby notified that
any review, dissemination, distribution or copying of
this message is strictly prohibited. This communica-
tion is for information purposes only and should not
be regarded as an offer to sell or as a solicitation
of an offer to buy any financial product. Email trans-
mission cannot be guaranteed to be secure or error-
free. P6070214
|
|
From: Ashley P. <api...@co...> - 2008-08-01 17:19:18
|
On Fri, 2008-08-01 at 11:57 -0500, Richard Lynch wrote: > My version of valgrind/callgrind (3.2.1) does not list any such argument. > > What version are you using? valgrind-3.3.0-Debian. The --help option gives you options for the currently selected tool, you have to use this command to see the callgrind options. valgrind --tool=callgrind --help |