|
From: Padala D. <pad...@gm...> - 2019-01-25 10:00:42
|
Hi My system has 4GB memory ( arm-linux ) . But when I try to run the valgrind, the process becomes very slow, and it gets rebooted with a message "valgrind: the 'impossible' happened' How much RAM is expected to be present in the system to run valgrind for 15-20 mins atleast. If i stop the process, before 100% memory gets over, it dumps the evaluation till that point. But it is only for 5 mins of Run. and it has not hit all the threads as the process is running slowly. ==1382== Memcheck, a memory error detector ==1382== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1382== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==1382== Command: Frm20xd ==1382== --1382-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --1382-- si_code=1; Faulting address: 0xFFFF0FE3; sp: 0x426987b0 valgrind: the 'impossible' happened: Killed by fatal signal host stacktrace: ==1382== at 0x58184470: getUIntLittleEndianly (guest_arm_toIR.c:196) ==1382== by 0x58184470: disInstr_ARM_WRK.isra.36 (guest_arm_toIR.c:16118) ==1382== by 0x5818E2B3: disInstr_ARM (guest_arm_toIR.c:23690) ==1382== by 0x581501D3: bb_to_IR (guest_generic_bb_to_IR.c:365) ==1382== by 0x581328AF: LibVEX_FrontEnd (main_main.c:560) ==1382== by 0x58133043: LibVEX_Translate (main_main.c:1185) ==1382== by 0x58059CBB: vgPlain_translate (m_translate.c:1813) ==1382== by 0x58095F53: handle_chain_me (scheduler.c:1134) ==1382== by 0x58097FFF: vgPlain_scheduler (scheduler.c:1483) ==1382== by 0x580F0F27: thread_wrapper (syswrap-linux.c:103) ==1382== by 0x580F0F27: run_a_thread_NORETURN (syswrap-linux.c:156) ==1382== by 0xFFFFFFFF: ??? Once I stop the process before it gets exited like above, It is dumping the evaluation it was doing. = ==1375== Process terminating with default action of signal 2 (SIGINT) ==1375== at 0x53B90E8: std::string::_Rep::_S_create(unsigned int, unsigned int, std::allocator<char> const&) (in /lib/libstdc++.so.6.0.17) ==1375== by 0x7DD155E7: ??? ==1375== ==1375== HEAP SUMMARY: ==1375== in use at exit: 16,558 bytes in 292 blocks ==1375== total heap usage: 1,449 allocs, 1,157 frees, 53,262 bytes allocated ==1375== ==1375== LEAK SUMMARY: ==1375== definitely lost: 0 bytes in 0 blocks ==1375== indirectly lost: 0 bytes in 0 blocks ==1375== possibly lost: 0 bytes in 0 blocks ==1375== still reachable: 16,558 bytes in 292 blocks ==1375== of which reachable via heuristic: ==1375== stdstring : 5,178 bytes in 194 blocks ==1375== suppressed: 0 bytes in 0 blocks ==1375== Rerun with --leak-check=full to see details of leaked memory ==1375== ==1375== For counts of detected and suppressed errors, rerun with: -v ==1375== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Thanks & Regards, Dileep Padala |
|
From: Alan C. <ala...@gm...> - 2019-01-25 10:10:35
|
I run it often on my Raspberry Pi 3b with 1 GB, never thought about it. Sent from my Motorola XT1527 On Fri, Jan 25, 2019, 5:02 AM Padala Dileep <pad...@gm...> wrote: > Hi > > My system has 4GB memory ( arm-linux ) . But when I try to run the > valgrind, the process becomes very slow, and it gets rebooted with a > message "valgrind: the 'impossible' happened' > > How much RAM is expected to be present in the system to run valgrind for > 15-20 mins atleast. > > > If i stop the process, before 100% memory gets over, it dumps the > evaluation till that point. > But it is only for 5 mins of Run. and it has not hit all the threads as > the process is running slowly. > > > ==1382== Memcheck, a memory error detector > > ==1382== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > > ==1382== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info > > ==1382== Command: Frm20xd > > ==1382== > > --1382-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) > - exiting > > --1382-- si_code=1; Faulting address: 0xFFFF0FE3; sp: 0x426987b0 > > > > valgrind: the 'impossible' happened: > > Killed by fatal signal > > > > host stacktrace: > > ==1382== at 0x58184470: getUIntLittleEndianly (guest_arm_toIR.c:196) > > ==1382== by 0x58184470: disInstr_ARM_WRK.isra.36 > (guest_arm_toIR.c:16118) > > ==1382== by 0x5818E2B3: disInstr_ARM (guest_arm_toIR.c:23690) > > ==1382== by 0x581501D3: bb_to_IR (guest_generic_bb_to_IR.c:365) > > ==1382== by 0x581328AF: LibVEX_FrontEnd (main_main.c:560) > > ==1382== by 0x58133043: LibVEX_Translate (main_main.c:1185) > > ==1382== by 0x58059CBB: vgPlain_translate (m_translate.c:1813) > > ==1382== by 0x58095F53: handle_chain_me (scheduler.c:1134) > > ==1382== by 0x58097FFF: vgPlain_scheduler (scheduler.c:1483) > > ==1382== by 0x580F0F27: thread_wrapper (syswrap-linux.c:103) > > ==1382== by 0x580F0F27: run_a_thread_NORETURN (syswrap-linux.c:156) > > ==1382== by 0xFFFFFFFF: ??? > > > > Once I stop the process before it gets exited like above, It is dumping > the evaluation it was doing. > > > > = > > ==1375== Process terminating with default action of signal 2 (SIGINT) > > ==1375== at 0x53B90E8: std::string::_Rep::_S_create(unsigned int, > unsigned int, std::allocator<char> const&) (in /lib/libstdc++.so.6.0.17) > > ==1375== by 0x7DD155E7: ??? > > ==1375== > > ==1375== HEAP SUMMARY: > > ==1375== in use at exit: 16,558 bytes in 292 blocks > > ==1375== total heap usage: 1,449 allocs, 1,157 frees, 53,262 bytes > allocated > > ==1375== > > ==1375== LEAK SUMMARY: > > ==1375== definitely lost: 0 bytes in 0 blocks > > ==1375== indirectly lost: 0 bytes in 0 blocks > > ==1375== possibly lost: 0 bytes in 0 blocks > > ==1375== still reachable: 16,558 bytes in 292 blocks > > ==1375== of which reachable via heuristic: > > ==1375== stdstring : 5,178 bytes in 194 > blocks > > ==1375== suppressed: 0 bytes in 0 blocks > > ==1375== Rerun with --leak-check=full to see details of leaked memory > > ==1375== > > ==1375== For counts of detected and suppressed errors, rerun with: -v > > ==1375== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) > > > > Thanks & Regards, > > Dileep Padala > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |
|
From: Tom H. <to...@co...> - 2019-01-25 10:21:46
|
On 25/01/2019 10:00, Padala Dileep wrote: > My system has 4GB memory ( arm-linux ) . But when I try to run the > valgrind, the process becomes very slow, and it gets rebooted with a > message "valgrind: the 'impossible' happened' > > How much RAM is expected to be present in the system to run valgrind > for 15-20 mins atleast. There's no fixed number because it entirely depends on what you are running valgrind on and which tool you are using. Using the default tool (memcheck) which you appear to be you will typically need a litle over double the memory your program would need without valgrind because memcheck is keeping shadow state to tell it which bits of your programs memory are initialised. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: Dallman, J. <joh...@si...> - 2019-01-25 10:28:17
|
The memory requirement for Valgrind is “several times as much memory as the application you’re testing needs without Valgrind.” How much memory does your application use normally? -- John Dallman From: Padala Dileep [mailto:pad...@gm...] Sent: 25 January 2019 10:00 To: val...@li... Subject: [Valgrind-users] What is the memory ( RAM ) requirement for running valgrind Hi My system has 4GB memory ( arm-linux ) . But when I try to run the valgrind, the process becomes very slow, and it gets rebooted with a message "valgrind: the 'impossible' happened' How much RAM is expected to be present in the system to run valgrind for 15-20 mins atleast. If i stop the process, before 100% memory gets over, it dumps the evaluation till that point. But it is only for 5 mins of Run. and it has not hit all the threads as the process is running slowly. ==1382== Memcheck, a memory error detector ==1382== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1382== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==1382== Command: Frm20xd ==1382== --1382-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --1382-- si_code=1; Faulting address: 0xFFFF0FE3; sp: 0x426987b0 valgrind: the 'impossible' happened: Killed by fatal signal host stacktrace: ==1382== at 0x58184470: getUIntLittleEndianly (guest_arm_toIR.c:196) ==1382== by 0x58184470: disInstr_ARM_WRK.isra.36 (guest_arm_toIR.c:16118) ==1382== by 0x5818E2B3: disInstr_ARM (guest_arm_toIR.c:23690) ==1382== by 0x581501D3: bb_to_IR (guest_generic_bb_to_IR.c:365) ==1382== by 0x581328AF: LibVEX_FrontEnd (main_main.c:560) ==1382== by 0x58133043: LibVEX_Translate (main_main.c:1185) ==1382== by 0x58059CBB: vgPlain_translate (m_translate.c:1813) ==1382== by 0x58095F53: handle_chain_me (scheduler.c:1134) ==1382== by 0x58097FFF: vgPlain_scheduler (scheduler.c:1483) ==1382== by 0x580F0F27: thread_wrapper (syswrap-linux.c:103) ==1382== by 0x580F0F27: run_a_thread_NORETURN (syswrap-linux.c:156) ==1382== by 0xFFFFFFFF: ??? Once I stop the process before it gets exited like above, It is dumping the evaluation it was doing. = ==1375== Process terminating with default action of signal 2 (SIGINT) ==1375== at 0x53B90E8: std::string::_Rep::_S_create(unsigned int, unsigned int, std::allocator<char> const&) (in /lib/libstdc++.so.6.0.17) ==1375== by 0x7DD155E7: ??? ==1375== ==1375== HEAP SUMMARY: ==1375== in use at exit: 16,558 bytes in 292 blocks ==1375== total heap usage: 1,449 allocs, 1,157 frees, 53,262 bytes allocated ==1375== ==1375== LEAK SUMMARY: ==1375== definitely lost: 0 bytes in 0 blocks ==1375== indirectly lost: 0 bytes in 0 blocks ==1375== possibly lost: 0 bytes in 0 blocks ==1375== still reachable: 16,558 bytes in 292 blocks ==1375== of which reachable via heuristic: ==1375== stdstring : 5,178 bytes in 194 blocks ==1375== suppressed: 0 bytes in 0 blocks ==1375== Rerun with --leak-check=full to see details of leaked memory ==1375== ==1375== For counts of detected and suppressed errors, rerun with: -v ==1375== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Thanks & Regards, Dileep Padala ----------------- Siemens Industry Software Limited is a limited company registered in England and Wales. Registered number: 3476850. Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD. |