|
From: Mandy M. <te...@ho...> - 2016-02-14 16:48:46
|
Hi , how to resolve this issue, invalid read of size 4 and Process terminating with default action of signal 11 (SIGSEGV) ? martin@ubuntu:~/Downloads/tasks$ valgrind --leak-check=yes casio_system valgrind: casio_system: command not found martin@ubuntu:~/Downloads/tasks$ valgrind --leak-check=yes ./casio_system ==15478== Memcheck, a memory error detector ==15478== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==15478== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==15478== Command: ./casio_system ==15478== Usage: ./casio_system file_name (system configuration) ==15478== ==15478== HEAP SUMMARY: ==15478== in use at exit: 0 bytes in 0 blocks ==15478== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==15478== ==15478== All heap blocks were freed -- no leaks are possible ==15478== ==15478== For counts of detected and suppressed errors, rerun with: -v ==15478== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) martin@ubuntu:~/Downloads/tasks$ valgrind --leak-check=yes ./casio_system a ==15479== Memcheck, a memory error detector ==15479== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==15479== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==15479== Command: ./casio_system a ==15479== ==15479== Invalid read of size 4 ==15479== at 0x40FFB4B: fgets (iofgets.c:50) ==15479== by 0x8048D36: get_casio_tasks_config_info (in /home/martin/Downloads/tasks/casio_system) ==15479== by 0x8048E95: main (in /home/martin/Downloads/tasks/casio_system) ==15479== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==15479== ==15479== ==15479== Process terminating with default action of signal 11 (SIGSEGV) ==15479== Access not within mapped region at address 0x0 ==15479== at 0x40FFB4B: fgets (iofgets.c:50) ==15479== by 0x8048D36: get_casio_tasks_config_info (in /home/martin/Downloads/tasks/casio_system) ==15479== by 0x8048E95: main (in /home/martin/Downloads/tasks/casio_system) ==15479== If you believe this happened as a result of a stack ==15479== overflow in your program's main thread (unlikely but ==15479== possible), you can try to increase the size of the ==15479== main thread stack using the --main-stacksize= flag. ==15479== The main thread stack size used in this run was 8388608. ==15479== ==15479== HEAP SUMMARY: ==15479== in use at exit: 0 bytes in 0 blocks ==15479== total heap usage: 1 allocs, 1 frees, 352 bytes allocated ==15479== ==15479== All heap blocks were freed -- no leaks are possible ==15479== ==15479== For counts of detected and suppressed errors, rerun with: -v ==15479== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Segmentation fault (core dumped) Regards, Martin ________________________________ From: Mandy Martino <te...@ho...> Sent: Sunday, February 14, 2016 23:25 To: val...@li... Subject: [Valgrind-users] what are the commands to check this scheduler code? Hi There is a need to recompile kernel to patch this module, how to check and step by step debug run this scheduler with valgrind before patch to kernel ? what are the commands to check this scheduler code? http://www.embedded.com/design/operating-systems/4204980/Real-Time-Linux-Scheduling-Part-3 [http://www.embedded.com/content/images/icons/contentitem-default.png]<http://www.embedded.com/design/operating-systems/4204980/Real-Time-Linux-Scheduling-Part-3> Implementing a new real-time scheduling policy for Linux ...<http://www.embedded.com/design/operating-systems/4204980/Real-Time-Linux-Scheduling-Part-3> www.embedded.com Implementing a new real-time scheduling policy for Linux: Part 3. Paulo Baltarejo Sousa and Luis Lino Ferreira, Polytechnic Institute of Porto July 28 ... Regards, Martin |