On Sun, 14 Jul 2024 12:45:06 +0100 jon bird <j...@onasticksoftware.co.uk> wrote:
>Hi Andreas, > >On Sun, 14 Jul 2024 13:16:02 +0200 >Andreas Rönnquist <andr...@ronnquist.net> wrote: > >> On Sun, 14 Jul 2024 09:45:19 +0100 >> jon <j...@onasticksoftware.co.uk> wrote: >[...] > >> >> Thanks for your report - Are you saying that you get "Illegal >> instruction" when running from the command line? - Could you please >> provide the full command-line output? >> >That's literally all that comes out on the command line: > >jon@lapdog:~$ filezilla >Illegal instruction >jon@lapdog:~$ > >> Also, which desktop environment are you on? - I have tested on amd64 >> Xfce and Gnome and cannot reproduce there, and cannot reproduce on >> i386 Gnome either. >> >This is on a fairly elderly Celeron laptop running LXQt. I half >wondered if the processor is too old - for info, o/p of /proc/cpuinfo: Thanks - that looks indeed like it might be the problem - however, some debugging would help out to pinpoint it exactly. > >And if it helps, backtrace from gdb: > >Program received signal SIGILL, Illegal instruction. >0xb7e804c3 in ?? () from >/lib/i386-linux-gnu/libfzclient-private-3.63.0.so (gdb) bt >#0 0xb7e804c3 in () at >/lib/i386-linux-gnu/libfzclient-private-3.63.0.so #1 0xb7e83c82 in >register_options(std::initializer_list<option_def>) () > at /lib/i386-linux-gnu/libfzclient-private-3.63.0.so >#2 0xb7dede0e in () at >/lib/i386-linux-gnu/libfzclient-private-3.63.0.so #3 0xb7fcfb43 in >call_init (env=0xbffff2ac, argv=0xbffff2a4, argc=1, l=<optimized out>) >at ./elf/dl-init.c:74 #4 call_init (l=<optimized out>, argc=1, >argv=0xbffff2a4, env=0xbffff2ac) at ./elf/dl-init.c:26 #5 0xb7fcfc3b >in _dl_init (main_map=<optimized out>, argc=1, argv=0xbffff2a4, >env=0xbffff2ac) at ./elf/dl-init.c:121 #6 0xb7fe64f0 in >_dl_start_user () at /lib/ld-linux.so.2 > Thanks - that can be helpful - however, could you please install the debug-symbols for the filezilla packages which would give more information - simplest is probably to get the packages directly here: http://debug.mirrors.debian.org/debian-debug/pool/main/f/filezilla/filezilla-dbgsym_3.63.0-1+deb12u3_i386.deb http://debug.mirrors.debian.org/debian-debug/pool/main/libf/libfilezilla/libfilezilla34-dbgsym_0.41.0-2_i386.deb or you can add the debug repos to your sources.list like described in the wiki here: https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols And then install them using apt (filezilla-dbgsym and libfilezilla34-dbgsym). Either of these methods should give a more detailed backtrace which makes it easier to pinpoint the problem. Thank you for your help. /Andreas andr...@ronnquist.net gus...@debian.org
