![]() Reading symbols from /bin/true.(no debugging symbols found).done.Īs you can see from the above, I am running a preemptable kernel from the ELRepo Project and am able to start up gdb on the true binary without any segmentation fault. ![]() This GDB was configured as "i386-redhat-linux-gnu".įor bug reporting instructions, please see: There is NO WARRANTY, to the extent permitted by law. This is free software: you are free to change and redistribute it. License GPLv3+: GNU GPL version 3 or later GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-32.el5_6.2)Ĭopyright (C) 2009 Free Software Foundation, Inc. # CONFIG_PREEMPT_TRACER is not Desktop]$ gdb /bin/true ![]() Running the standalone bootable version of memtest86+ for at least 24 hours would be my immediate Desktop]$ uname Desktop]$ grep -i preempt /boot/config-$(uname -r) Indeed, the first thing I always check when a segmentation fault occurs is the system memory. Logically, a change of kernel preemption model should not result in the issue you are experiencing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |