|
From: Joshua Moore-O. <jo...@ch...> - 2004-04-21 17:28:06
|
Ok, so I need to valgrind a program that contains epoll. Now, valgrind is telling me that I can't run the program using epoll... and I have no idea how ti implement the system call myself.. This may be a laughable question, but is there a way to just get valgrind to nto debug the epoll system call and just debug the rest of the code? Or even better is there a cvs version//patch for valgrind that will let me debug epoll programs? Thanks, Joshua Moore-Oliva |
|
From: Tom H. <th...@cy...> - 2004-04-21 17:32:01
|
In message <200...@ch...>
Joshua Moore-Oliva <jo...@ch...> wrote:
> Ok, so I need to valgrind a program that contains epoll.
>
> Now, valgrind is telling me that I can't run the program using epoll...
> and I have no idea how ti implement the system call myself..
>
> This may be a laughable question, but is there a way to just get valgrind
> to nto debug the epoll system call and just debug the rest of the code?
>
> Or even better is there a cvs version//patch for valgrind that will let me
> debug epoll programs?
A quick grep of the source suggests that 2.1.1 has epoll support.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Joshua Moore-O. <jo...@ch...> - 2004-04-21 17:36:03
|
I installed valgrind 2.1.1 and now whenever I run
valgrind ./a.out
I get this.. it refuses to run any programs?
I'm using glibc 2.3.3-pre
valgrind ./a.out
usage: valgrind --tool=<toolname> [options] prog-and-args
common user options for all Valgrind tools, with defaults in [ ]:
--tool=<name> Use the Valgrind tool named <name>
--help show this message
--help-debug show this message, plus debugging options
--version show version
-q --quiet run silently; only print error msgs
-v --verbose be more verbose, incl counts of errors
--trace-children=no|yes Valgrind-ise child processes? [no]
--track-fds=no|yes Track open file descriptors? [no]
uncommon user options for all Valgrind tools:
--run-libc-freeres=no|yes Free up glibc memory at exit? [yes]
--weird-hacks=hack1,hack2,... [none]
recognised hacks are: ioctl-VTIME truncate-writes lax-ioctls
--signal-polltime=<time> time, in mS, we should poll for signals.
Only applies for older kernels which need
signal routing [50]
--lowlat-signals=no|yes improve wake-up latency when a thread receives
a signal [no]
--lowlat-syscalls=no|yes improve wake-up latency when a thread's
syscall completes [no]
--pointercheck=no|yes enforce client address space limits [yes]
user options for Valgrind tools that report errors:
--logfile-fd=<number> file descriptor for messages [2=stderr]
--logfile=<file> log messages to <file>.pid<pid>
--logsocket=ipaddr:port log messages to socket ipaddr:port
--demangle=no|yes automatically demangle C++ names? [yes]
--num-callers=<number> show <num> callers in stack traces [4]
--error-limit=no|yes stop showing new errors if too many? [yes]
--show-below-main=no|yes continue stack traces below main() [no]
--suppressions=<filename> suppress errors described in <filename>
--gen-suppressions=no|yes print suppressions for errors detected [no]
--db-attach=no|yes start debugger when errors detected? [no]
--db-command=<command> command to start debugger [gdb -nw %f %p]
--input-fd=<number> file descriptor for input [0=stdin]
Extra options read from ~/.valgrindrc, $VALGRIND_OPTS, ./.valgrindrc
Valgrind is Copyright (C) 2000-2004 Julian Seward
and licensed under the GNU General Public License, version 2.
Bug reports, feedback, admiration, abuse, etc, to: valgrind.kde.org.
Tools are copyright and licensed by their authors. See each
tool's start-up message for more information.
On April 21, 2004 1:32 pm, Tom Hughes wrote:
> In message <200...@ch...>
> Joshua Moore-Oliva <jo...@ch...> wrote:
>
> > Ok, so I need to valgrind a program that contains epoll.
> >
> > Now, valgrind is telling me that I can't run the program using epoll...
> > and I have no idea how ti implement the system call myself..
> >
> > This may be a laughable question, but is there a way to just get valgrind
> > to nto debug the epoll system call and just debug the rest of the code?
> >
> > Or even better is there a cvs version//patch for valgrind that will let me
> > debug epoll programs?
>
> A quick grep of the source suggests that 2.1.1 has epoll support.
>
> Tom
>
|
|
From: Andrew C. <and...@ya...> - 2004-04-21 17:39:20
|
On Wednesday 21 Apr 2004 18:44, Joshua Moore-Oliva wrote: > I installed valgrind 2.1.1 and now whenever I run > > valgrind ./a.out Use valgrind --tool=memcheck ./a.out (or specify a different --tool=...) Andrew |
|
From: Tom H. <th...@cy...> - 2004-04-21 17:39:52
|
In message <200...@ch...>
Joshua Moore-Oliva <jo...@ch...> wrote:
> I installed valgrind 2.1.1 and now whenever I run
>
> valgrind ./a.out
>
> I get this.. it refuses to run any programs?
You haven't specified which tool to use - there is no longer a
default tool so you will need this:
valgrind --tool=memcheck ./a.out
You can add "--tool=memcheck" to ~/.valgrindrc if you want to make
it the default.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Joshua Moore-O. <jo...@ch...> - 2004-04-21 17:42:01
|
Ignore me, I did not realise that I now have to explicitly specify --tool=memcheck. Joshua Moore-Oliva |