Solved Firefox segfault and go further on this gdb infos (useless for me)

[piggy]

I have this firefox segfault on startup on one machine running firefox

FreeBSD 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC  i386

I try to get some debug infos and I get

/usr/local/bin # /usr/libexec/gdb /usr/local/bin/firefox     GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)...
(gdb) break main
Function "main" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y

Breakpoint 1 (main) pending.
(gdb) run
Starting program: /usr/local/bin/firefox

Program received signal SIGSEGV, Segmentation fault.
0x21309260 in ?? ()
(gdb) bt
#0  0x21309260 in ?? ()
#1  0x21340a3c in ?? ()
#2  0x21329370 in ?? ()
#3  0x2103cf0a in ?? ()
#4  0x00000000 in ?? ()
(gdb) info sharedlibrary
No shared libraries loaded at this time.
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y

Starting program: /usr/local/bin/firefox

Program received signal SIGSEGV, Segmentation fault.
0x21309260 in ?? ()

Maybe for someone in this forum this isn't useless so he/she can help me to troubleshoot this problem or get more from gdb. For the rest of his use, this box run perfectly fine.

Thankx

 

[piggy]

The system resolved the problem itself. After a batch of ports updates, between them some system component like Python, Node and others , the problem went resolved by itself. No need to recompile Firefox, it just stopped segfault on start. Now I'm curious to understand what and how it was resolved (it is sure the problems wasn't in Firefox itself considering it started work without the need to rebuild). Now considering the problem was affecting also Thunderbird and Cliqz (they do pretty much share the same code base and developing tools) and they all started work again without rebuild them, the culprit was a sytem component. Which one? This is the mistery I do have any idea how to discover.