SeaMonkey 1.1.19 segfaults at startup

[BarryK]

I have compiled this very old version of SeaMonkey. Version 1.1.19 was released in 2010.

I have managed to compile it in EasyOS, which has glibc 2.33 and gcc 9.3.0. Unfortunately, it segfaults at startup. Here are my notes:

https://bkhome.org/news/202111/seamonke ... asyos.html

Back in my Windows programming days, prior to 2003, I used a Borland Debugger with text-mode GUI, to trace programs and find where faults such as a crash were occurring. Was able to view the source code and set breakpoints. It was a great tool.

With Linux though, hardly know anything about how to find where the segfault is occurring. A long time ago, I did briefly use the 'gdb' debugger utility, which I recall is just a simple CLI interface. There is something else called 'strace' I think, don't know anything about it.

Does anyone know of a good online guide to help with find the cause of the segfault?

Tonight I plan to recompile SM 1.1.19, leaving in the debugging symbols.

[mikewalsh]

@BarryK :-

Perhaps there might be something of use here, Barry:-

https://www.ubuntupit.com/best-linux-de ... engineers/

Worth a look, perhaps.

Mike.

[Grey]

A small "zoo" of tools: https://reverseengineering.stackexchang ... al-ida-pro

[williams2]

Often, incompatible shared object library files can cause a segfault.

https://www.cprogramming.com/debugging/segfaults.html

https://www.cprogramming.com/debugging/valgrind.html

[BarryK]

@BarryK :-

Perhaps there might be something of use here, Barry:-

https://www.ubuntupit.com/best-linux-de ... engineers/

Worth a look, perhaps.

Mike,
That's a great link! Thanks very much.

I have compiled Nemiver debugger. It is a GUI for gdb. A gnome app, and it wanted various gnome dependencies, but I finally managed to compile it.

So far, have only started it, to check that it does run, haven't used it for anything yet.

I will create a PET later today, along with it's deps. Though, if you have one of the Debian or Ubuntu-based pups it might already be available in the repo.

[BarryK]

Often, incompatible shared object library files can cause a segfault.

https://www.cprogramming.com/debugging/segfaults.html

https://www.cprogramming.com/debugging/valgrind.html

Thanks, that first link is great information getting started with using gdb to find where the app is segfaulting.

[don570]

JF who is one of the main coders of pine64 recommends JetBrains CLion for debugging.
30 day free trial

https://twitter.com/codingfield/status/ ... 9530113025
https://twitter.com/clion_ide/status/14 ... 9470714880
___________________________________________________