I'm not sure why you're mailing the LAM/MPI mailing list with a valgrind
question.
We can't really answer questions about valgrind; you probably want to use
the e-mail address that's in the error message that you cut-n-pasted
(jseward_at_[hidden]). I think he's the author/maintainer of valgrind.
On Tue, 18 Nov 2003, rajesh wrote:
> hi all,
> I am very new to Valgrind tool. Seems very interesting to use when i saw
> the valgrind-howto in tldp. So I downloaded this and trying to use the
> same for my project.
> My project is working with 6 threads and a main thread. When I am
> running the project with out this tool it will work OK. But later in
> some point of time, the project got SIGSEGV. I wish to get trace the
> problem of my project with this tool.
> So I downloaded valgrind-2.0.0 from net and installed successfully in my
> system. And I tried to understand the messages and other stuffs of the
> logs by writing some test codes. I felt good.
> So I tried the same with my project also, at that time my project
> terminates at the early stage itself. And later, when I checked the log
> file which i captured by stderr redirection, I found some problematic
> statements as bellow:
>
> ==1619== Syscall param writev(vector[...]) contains uninitialised or
> unaddressable byte(s)
> ==1619== at 0x40186BA7: vgAllRoadsLeadToRome_writev (vg_intercept.c:117)
> ==1619== by 0x40186BE8: __writev (vg_intercept.c:774)
> ==1619== by 0x407CEC95: (within /usr/X11R6/lib/libX11.so.6.2)
> ==1619== by 0x407CF7A6: _X11TransWritev (in /usr/X11R6/lib/libX11.so.6.2)
> ==1619== Address 0x43E94C3E is 118 bytes inside a block of size 4200
> alloc'd
> ==1619== at 0x4002BB54: malloc (vg_replace_malloc.c:153)
> ==1619== by 0x407B5E1B: _XAllocScratch (in /usr/X11R6/lib/libX11.so.6.2)
> ==1619== by 0x407A9BD5: (within /usr/X11R6/lib/libX11.so.6.2)
> ==1619== by 0x407A9F44: (within /usr/X11R6/lib/libX11.so.6.2)
> ==1619== valgrind's libpthread.so: UNIMPLEMENTED FUNCTION: tcdrain
> ==1619==
> valgrind's libpthread.so: Please report this bug to me at: jseward_at_[hidden]
>
> Can you pls help me in this context, how to trace the same project from this
> tool.
>
> Expecting speedy reply...
> Thanx in advance...
> -Rajesh
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
