By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,870 Members | 1,212 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,870 IT Pros & Developers. It's quick & easy.

Valgrind: problem opening proc/self/maps

P: n/a
Hi all,

I'm testing an application using valgrind 3.2.0 unter Linux kernel 2.4.
When the test are finished and the app terminates valgrind gives the
error:

--15631:0:aspacem Valgrind: FATAL: I/O error on /proc/self/maps
--15631:0:aspacem Exiting now.

My first thought was that I need more access rights on that file, but
my user can do a "cat /proc/self/maps" - so this shouldn't be the
problem.

Does anybody know a solution for this?

Best regards
Markus

Oct 24 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
mfried wrote:
I'm testing an application using valgrind 3.2.0 unter Linux kernel
2.4. When the test are finished and the app terminates valgrind gives
the error:

--15631:0:aspacem Valgrind: FATAL: I/O error on /proc/self/maps
--15631:0:aspacem Exiting now.

My first thought was that I need more access rights on that file, but
my user can do a "cat /proc/self/maps" - so this shouldn't be the
problem.

Does anybody know a solution for this?
Somebody probably knows, but comp.lang.c++ is NOT the right place to
discuss it. Please visit http://www.valgrind.org/ and find the info
on how to ask them or others questions on using the product.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
Oct 24 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.