> If you can find the coredump file and do the backtrace on that file, that
> would be helpful, so we can see where the segfault is actually happening.
> These files which are their file extensión?
I tried to identify segfault (core files) and I did not find them
for i in `find / -name core -print 2>/dev/null`
do
file $i | grep "core file" >/dev/null
if [ $? -eq 0 ]; then
file $i
fi
done
/root/core: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style,
from '/usr/lib/vmware-tools/sbin64/vmtoolsd -n vmusr', real uid: 0, effective
uid: 0, real gid: 0, effective gid: 0, execfn:
'/usr/lib/vmware-tools/sbin64/vmtoolsd', platform: 'x86_64'
Is there any another way to identify these segfaults which are mentioned in
/var/log/message file? To check which is their problema cause.
Jun 7 10:33:30 tmxqrocnsG5 kernel: [202742.808204] guacd[146842]: segfault at
10 ip 00007fa1fc3e3622 sp 00007fa00f66dc80 error 4 in
libguac-client-rdp.so.0.0.0[7fa1fc3d1000+1a000]
Jun 7 10:33:30 tmxqrocnsG5 kernel: [202742.808310] Code: 00 be 03 00 00 00 48
89 ef e8 8a e9 fe ff b8 01 00 00 00 e9 7a ff ff ff 53 48 8b 07 48 89 fb 48 89
de 48 8b 40 10 48 8b 40 20 <48> 8b 78 10 e8 25 e9 fe ff 8b 43 18 85 c0 74 0e 31
c0 5b c3 66 2e
-Gabriel
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
