gcmd-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gcmd-dev] Segfault


From: Mamoru TASAKA
Subject: Re: [gcmd-dev] Segfault
Date: Wed, 24 Nov 2021 22:50:44 +0900
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0

Greg wrote on 2021/11/24 11:01:

On 11/23/21 16:28, Uwe Scholz wrote:
Hi Greg,

Am Tue, 23 Nov 2021 10:43:46 -0500 schrieb Greg:
Hi, Yesterday I installed GC from the master git repo.. Everything went
fine and I ran sudo gnome-commander and it ran just fine.. I was a happy
camper.. I ran it under my normal user 'greg' and all was well.. I
installed a few programs I use and tried to run GC as root,but got a
segfault...

          The only changes I made in GC was bookmarking my hard
drives,that seems to work fine also..

Here is a snippet from the syslog:


ov 22 11:50:37 TVserver dbus-daemon[31885]: [session uid=0 pid=31883]
Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=0
pid=79639 comm="gnome-commander " label="unconfined")
Nov 22 11:50:38 TVserver dbus-daemon[31885]: [session uid=0 pid=31883]
Successfully activated service 'ca.desrt.dconf'
Nov 22 12:00:07 TVserver kernel: [ 3456.280718] gnome-commander[79639]:
segfault at 28 ip 000055cd5d8298c5 sp 00007ffecf80e160 error 4 in
gnome-commander[55cd5d7df000+ab000]
Nov 22 12:00:07 TVserver kernel: [ 3456.280749] Code: e8 b0 bc fb ff 48
83 c4 08 48 89 c7 e9 24 13 02 00 0f 1f 40 00 f3 0f 1e fa 41 56 41 55 41
54 49 89 f4 55 48 89 fd 48 83 ec 08 <48> 8b 47 28 48 8b 00 48 85 c0 74
6f 48 83 78 08 00 74 68 48 8b 7d
Thank you Greg for putting effort in this. From the syslog excerpt
above one cannot see what actually happened. You might give if it try
and create a stack trace from which one can extract more information.

In the recent discussion to #108 you can find a way how to do this:
https://gitlab.gnome.org/GNOME/gnome-commander/-/issues/108

Also, you can start Gcmd with "gnome-commander -d a" for enabling debug
output (which is not as informative as a stack trace).

I can only suspect for the moment. Probably when creating a device
entry for your system something went wrong and now Gcmd cannot
interpret the stored item correctly, resulting in the crash?

Hope I could help a bit.

Best
Uwe

Uwe,

         Thanks for the reply..I have been running Linux since about 1994 and 
this is my first stack trace.. I hope it's correct and gives you the 
information you need.. I really appreciate the time and effort you put in to 
making Gnome-Commander the best file manager...

I have attached the text file containing the stack trace..

If you need any more information don't hesitate to ask..

Best regards, Greg


What does
sudo coredumpctl gdb --debugger-arguments="-batch -ex disassemble -ex up -ex 
disassemble -ex 'info all-registers'" 27858
say?

Mamoru



reply via email to

[Prev in Thread] Current Thread [Next in Thread]