Yes, makes sense. I opened a ticket a few days ago that pointed to
the beginning of this thread. It's just a matter of someone actually
going to do it. Might be useful to do both: maintain a suppression
file in the distribution and put something in the FAQ.
On Jun 9, 2009, at 6:31 PM, R
Sounds like the better solution to me! And far less work... ;-)
Perhaps if we post a valgrind suppression file on the OMPI web site,
and/or include it in our releases, we could help users avoid the
problems. We could update the file as more areas are identified so we
eventually have a reall
It is not as simple as it sound. The problem is not coming from the
OOB, it just surface there. The header we add on the wire is well
aligned and completely initialized. The problem is coming from the
buffer that the OOB TCP is asked to send, buffer which is only
partially initialized. This
We have done similar things in our code base, and I may explore that option
here. Doing it in too many places gets to be icky, though, so I'll have to
look at it before deciding on the course of action.
Thanks!
Ralph
On Tue, Jun 9, 2009 at 12:13 PM, tom fogal wrote:
> Ralph Castain writes:
>
Ralph Castain writes:
> I can't speak to all of the OMPI code, but I can certainly create
> a new configure option --valgrind-friendly that would initialize
> the OOB comm buffers and other RTE-related memory to eliminate such
> warnings.
That would be excellent, thank you for offering.
> I woul
On Tue, 2009-06-09 at 12:01 -0600, Ralph Castain wrote:
> I can't speak to all of the OMPI code, but I can certainly create a
> new configure option --valgrind-friendly that would initialize the OOB
> comm buffers and other RTE-related memory to eliminate such warnings.
>
> I would prefer to confi
I can't speak to all of the OMPI code, but I can certainly create a new
configure option --valgrind-friendly that would initialize the OOB comm
buffers and other RTE-related memory to eliminate such warnings.
I would prefer to configure it out rather than adding a bunch of "if-then"
checks for env
jody writes:
> I made a suppression file for the irrelevant memory leaks of ompi: I
> make no claim that it catches all possible ones, but it catches all
> that appear in my code.
[snip]
Thanks, Jody.
What are the chances something like this could be added / maintained in
the OpenMPI tree? It
I should add that the "..." are verbatim, not ellipses which indicate
that i left something out!
On Tue, Jun 9, 2009 at 3:43 PM, jody wrote:
> Hi
> I made a suppression file for the irrelevant memory leaks of ompi:
> I make no claim that it catches all possible ones, but it catches all
> that app
Hi
I made a suppression file for the irrelevant memory leaks of ompi:
I make no claim that it catches all possible ones, but it catches all
that appear in my code.
{
OMPI_Leaks-init-malloc
Memcheck:Leak
fun:malloc
...
fun:PMPI_Init
...
fun:main
}
{
OMPI_Leaks-init-malloc2
Memch
This is worth adding to the FAQ.
On Jun 9, 2009, at 2:31 AM, Ashley Pittman wrote:
On Mon, 2009-06-08 at 23:41 -0600, tom fogal wrote:
> George Bosilca writes:
> > There is a whole page on valgrind web page about this topic.
Please
> > read http://valgrind.org/docs/manual/manual-core.html#m
On Mon, 2009-06-08 at 23:41 -0600, tom fogal wrote:
> George Bosilca writes:
> > There is a whole page on valgrind web page about this topic. Please
> > read http://valgrind.org/docs/manual/manual-core.html#manual-core.suppress
> > for more information.
>
> Even better, Ralph (et al.) is if
George Bosilca writes:
> There is a whole page on valgrind web page about this topic. Please
> read http://valgrind.org/docs/manual/manual-core.html#manual-core.suppress
> for more information.
Even better, Ralph (et al.) is if we could just make valgrind think
this is defined memory. One c
There is a whole page on valgrind web page about this topic. Please
read http://valgrind.org/docs/manual/manual-core.html#manual-core.suppress
for more information.
george.
On Jun 8, 2009, at 15:24 , Ralph Castain wrote:
We deliberately choose to not initialize our msg buffers as this
t
We deliberately choose to not initialize our msg buffers as this takes
considerable time. Instead, we fill in only the portion required by a given
message, and then send only that much of the buffer. Thus, the uninitialized
portion is ignored.
I don't know of a way to tell valgrind to ignore it, I
Hi all,
I've configured a source build of OpenMPI 1.3.2 with valgrind enabled
[1], and I'm seeing a lot of errors with writev() when I run this under
valgrind. For example, with the following `hello, world' program:
#include
#include
int main(int argc, char *argv[]) {
MPI_Init(&argc
16 matches
Mail list logo
