Nemiver debugger now in devx SFS

Yesterday, I posted about compiling SeaMonkey 1.1.19 but it segfaulted at startup:

https://bkhome.org/news/202111/seamonkey-1119-compiled-in-easyos.html

I started a discussion about how to trace where in the code the segfault is occurring:

https://forum.puppylinux.com/viewtopic.php?t=4580

Mike (mikewalsh) responded with a great link that lists lots of Linux debugger/trace tools. The EasyOS devx SFS already has the 'gdb' CLI utility, and I saw on that link, there are 'ddd' and 'nemiver' GUI frontends for gdb.

I went for nemiver and compiled it. The project seems to be almost dead, but then, if it works, perhaps no need for more commits to the git repository. I chose version 0.8.2, not the latest, but it suited me to stay with a gtk+2 based app rather than gtk+3.

Two dependencies, 'gtkmm' and 'libgtop', are compiled in OpenEmbedded. I compiled 'libgtksourceviewmm' and 'nemiver' in a running EasyOS and made them into PETs.

Nemiver will be in the devx SFS in the next release of EasyOS.

Nemiver project page:

https://gitlab.gnome.org/Archive/nemiver

Regarding nemiver 0.8.2, the source code required fixes to compile with gcc 9.3.0. This is a problem with C++ code, the Gnu C++ compiler moves the goal posts with later versions.
I don't think that I will upload patches, but at least should upload my modified source tarball.

Haven't attempted to debug SeaMonkey 1.1.19 yet. First, I want to compile it with a different 'mozconfig' file. David W. sent me an email with a link to a 'mozconfig' file that was used to compile SM 1.1.19 and that has given me some thoughts about changes to the configuration ...that hopefully might result in an executable that doesn't segfault!

EDIT 2021-12-01:
Patched source uploaded:

http://distro.ibiblio.org/easyos/source/alphabetical/n/nemiver-0.8.2-p1.tar.gz    

Tags: easy