|
From: Yeshurun, M. <mei...@in...> - 2005-11-20 19:58:58
|
Could it be because a thread terminated and its stack was freed?
I thought the message means that the A bits of 148823752 consecutive
bytes were changed to indicate invalid addresses ("a 0").
Thanks,
Meir
-----Original Message-----
From: val...@li...
[mailto:val...@li...] On Behalf Of
Nicholas Nethercote
Sent: Sunday, November 20, 2005 7:28 PM
To: Tom Hughes
Cc: val...@li...
Subject: Re: [Valgrind-users] address range perms?
On Sun, 20 Nov 2005, Tom Hughes wrote:
>> Warning: set address range perms: large range 148823752, a 0, v 1
>
> It means that the addressability and/or definedness flags for a
> large area were changed in one go - the area has to be close to
> 100Mb in size before the warning triggers.
>
> It can sometimes be legitimate, but can sometimes indicate a problem.
And "problem" here is as likely to be a problem with Valgrind as it is a
problem with your program. You probably don't need to worry about it.
Is it likely that your program allocated 148MB at once, eg. on the heap?
Nick
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users
|
|
From: Julian S. <js...@ac...> - 2005-11-20 20:08:20
|
On Sunday 20 November 2005 19:58, Yeshurun, Meir wrote:
> Could it be because a thread terminated and its stack was freed?
>
> I thought the message means that the A bits of 148823752 consecutive
> bytes were changed to indicate invalid addresses ("a 0").
The encoding is backwards: 0 = valid, 1 = invalid. Hence this is an
area which is addressible but undefined, most likely the result of
doing malloc.
J
|