the number of events (and where they happened), but
maybe it wouldn't be too hard to modify it to print the address every
time a LLC miss happens. If anyone could point me to the right place
to look, I would appreciate it.
Th
.0.SVN-Debian on Ubuntu 10.04
32bit (kernel version 2.6.32-32-generic).
Thanks,
Martin Heller
--
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll g
by 0x3809AFF6: run_a_thread_NORETURN (syswrap-linux.c:98)
==27555==by 0x3809B352: vgModuleLocal_start_thread_NORETURN
(syswrap-linux.c:259)
==27555==by 0x3809E428: ??? (in
/usr/local/lib/valgrind/helgrind-x86-linux)
under
Memcheck).
Thanks,
Martin Heller
--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion
php?msg_id=27866368
Unfortunately I am far from being able to create a small program to
reproduce the crash.
Martin Heller
--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabili
;mutex);
std::cout << "finished" << std::endl;
return 0;
}
// CODE END
Martin Heller
--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilit
"The MPI functions to be wrapped
are assumed to be in an ELF shared object with soname matching libmpi.so*. This
is known to be correct at least for Open MPI and Quadrics MPI, and can easily
be changed if required."
How do I change that?
Thanks for your help!
Martin Kalany
--
NEU: F
Am 05.05.2012 16:38, schrieb Philippe Waroquiers:
> On Sat, 2012-05-05 at 14:25 +0200, Martin Kalany wrote:
>> Hello,
>>
>> I'm trying to use valgrind do debug an mpich2 program. Unfortunately, I get
>> the following error:
>>
>> libmpi.so.0: can
Am 05.05.2012 18:59, schrieb Philippe Waroquiers:
> On Sat, 2012-05-05 at 18:14 +0200, Martin Kalany wrote:
>>> Is the 'cannot open' error only there when running under Valgrind ?
>> Yes. When I use mpirun, it's fine.
>>
>> What I think is s
Am 06.05.2012 00:54, schrieb Philippe Waroquiers:
> On Sun, 2012-05-06 at 00:24 +0200, Martin Kalany wrote:
>>> Valgrind documation states that "The MPI functions to be wrapped are
>>> assumed to be in an ELF shared object with soname matching libmpi.so*. This
>>&
Am 07.05.2012 21:34, schrieb Dave Goodell:
> On May 7, 2012, at 2:15 PM CDT, Martin Kalany wrote:
>
>> Am 06.05.2012 00:54, schrieb Philippe Waroquiers:
>>> On Sun, 2012-05-06 at 00:24 +0200, Martin Kalany wrote:
>>>>> Valgrind documation states that
xts (suppressed: 0 from 0)
Segmentation fault
139|root@android:/data/local #
Do you have any idea what might be happening?
The crash appears to always happen on the same address, no matter what
application is being run.
Thanks
Martin
--
and not
a Linaro one mentioned in the README.android.
Could you point me to a Linaro image which is known to work with
Valgrind on Panda (preferably with graphics acceleration enabled)?
Thanks
Martin
On 07/11/2012 04:23 PM, Julian Seward wrote:
>
> Total guess, but maybe a problem with TLS s
d to look in C++ and Fortran too.
Thank you very much for your response.
Best regards,
Martin Beseda
--
___
Valgrind-users mailing list
Valgrind-users@lists.s
d in total.
Otherwise, for heap and stack you can use valgrind's massif.
Regards,
Martin
On 06.03.19 14:13, Mohsen Pahlevanzadeh wrote:
Dear all,
I need to find out size of my program main memory. How can I do it with
valgrind?
--regards
_
file descriptor 0: /dev/pts/1
==21285==
Isn't /dev/pts/1 my terminal?
I don't know if matters for this question, but I used the following options
for valgrind:
--tool=memcheck --leak-check=full --show-reachable=yes --num-callers=20
--track-fds=yes -v
Th
<5609530f.9070...@gmx.de>
> Content-Type: text/plain; charset=windows-1252
>
> Am 25.09.2015 um 22:27 schrieb martin:
> > I'm trying to do a memory trace of my application, but only for
> > operations that go to DRAM, that is, only if there was a LLC miss
&g
into
the debug build would be helpful. I appreciate your feedback.
Regards,
Martin
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
stack tracer like that.
The prettiest alternatives without Valgrind go along the lines of
https://eli.thegreenplace.net/2015/programmatic-access-to-the-call-stack-in-c/
using libunwind and cxxabi. This still is not as close to the source as
Valgrind's output.
Best,
Martin
On Mon, May 24, 20
19 matches
Mail list logo