Segfault message in dmesg
by deretsigernu from LinuxQuestions.org on (#5M33X)
Hi,
I recently changed my kernel from 4.4.19 to 5.10.14. I noticed in the dmesg log this segfault message:
Quote:
I don't know if this segfault is a problem? I haven't experience any kernel panics and I can run most of the apps I normally use.
I'm not sure if the switch in kernel is causing this message, but they did show up at the same time. I saw this thread, but I don't know what gdb does nor how to apply the information from the segfault message to gdb.
I tried:
Code:(gdb) run xcmddc
Starting program: xcmddc
No executable file specified.
Use the "file" or "exec-file" command.
(gdb) file /usr/bin/xcmddc
Reading symbols from /usr/bin/xcmddc...(no debugging symbols found)...done.
(gdb) exec-file /usr/bin/xcmddc
[crickets...]What should I do to deal with the segfault?
I recently changed my kernel from 4.4.19 to 5.10.14. I noticed in the dmesg log this segfault message:
Quote:
| [ 16.111271] xcmddc[793]: segfault at 0 ip 00007f560841cb5f sp 00007ffc98a9eac0 error 4 in libXcm.so.0.0.5[7f5608419000+8000] [ 16.111323] Code: b8 01 00 00 00 83 fb ff 74 34 31 c0 ba 50 00 00 00 be 03 07 00 00 89 df e8 5e e6 ff ff 85 c0 74 2a b8 02 00 00 00 49 8b 55 00 <80> 3a 00 75 0a 80 7a 01 ff 0f 84 82 00 00 00 b8 04 00 00 00 48 83 [ 16.111531] udevd[687]: '/usr/bin/xcmddc --i2c /dev/i2c-0 --identify' [793] terminated by signal 11 (Segmentation fault) |
I'm not sure if the switch in kernel is causing this message, but they did show up at the same time. I saw this thread, but I don't know what gdb does nor how to apply the information from the segfault message to gdb.
I tried:
Code:(gdb) run xcmddc
Starting program: xcmddc
No executable file specified.
Use the "file" or "exec-file" command.
(gdb) file /usr/bin/xcmddc
Reading symbols from /usr/bin/xcmddc...(no debugging symbols found)...done.
(gdb) exec-file /usr/bin/xcmddc
[crickets...]What should I do to deal with the segfault?