This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On Jun 19, 2008, at 11:25 AM, Gabriele Fatigati wrote:
> Hi Jeff,
> i solved using Gigabit net and eth1 interface!
> So, there are problems beetween Infiniband and gcc with bound
This is probably not too surprising -- the IB driver gives back memory
to the process that didn't come from malloc or other traditional
memory allocators, and this can confuse bounds checkers, leading to
In the upcoming v1.3 series, we added a whole pile of stuff to handle
these kinds of false positives when running under valgrind. Just
curious -- does the gcc bounds checking stuff give you the possibility
of saying "this memory is ok"? (valgrind does; we use it for IB-
driver allocated or initialized memory)