Bug 131020 - problems in starting the binary using valgrind with memcheck and addrcheck
Summary: problems in starting the binary using valgrind with memcheck and addrcheck
Status: RESOLVED INTENTIONAL
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 2.1.2
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-18 11:59 UTC by gupta
Modified: 2012-08-10 13:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description gupta 2006-07-18 11:59:33 UTC 
Hello all,

I have found the following error:

--18524-- Line number overflow detected (65221 --> 152) 
in /utran/fdd/nodeb/cc/ulm/cpn/globals/sdl/cpn_IDLPkg.c
==18524== Warning: file /utran/fdd/nodeb/cc/ulm/cpn/globals/sdl/cpn_IDLPkg.c is 
very big (> 65535 lines) Line numbers and annotation for this file might be 
wrong.  Sorry
--18524-- Line number overflow detected (65474 --> 26) 
in /utran/fdd/nodeb/cc/ulm/cpn/crm/sdl/crm_CRMPkg.c
==18524== Warning: file /utran/fdd/nodeb/cc/ulm/cpn/crm/sdl/crm_CRMPkg.c is 
very big (> 65535 lines) Line numbers and annotation for this file might be 
wrong.  Sorry

VG_(get_memory_from_mmap): newSuperblock's request for 12292096 bytes failed.
VG_(get_memory_from_mmap): 129675264 bytes already allocated.

Sorry.  You could try using a tool that uses less memory;
eg. addrcheck instead of memcheck.

-----------------------------------------------------------------------------
I tried using addrcheck but still got the same problem. I am using system with 
8GB RAM and 8 GHz processor.

Please help me in this matter.

Thanks in advance,

with best regards,
  Gupta.
Comment 1 Julian Seward 2006-07-18 13:36:19 UTC 
On Tuesday 18 July 2006 10:59, gupta wrote:
[bugs.kde.org quoted mail]

2.1.2 is an old version - many bugs have been fixed since then.
Try upgrading to 3.2.0.

J
Comment 2 Nicholas Nethercote 2006-07-18 13:38:25 UTC 
I will close this bug.  If you have the same problem with 3.2.0, please reopen it.