From: nunojsilva@invalid.invalid   
      
   On 2025-08-24, Dave Yeo wrote:   
      
   > bey24thgfdhg wrote:   
   >> When I sent the "Testing" message above I had launched SM from the   
   >> command line with seamonkey --mail to see if the crash resulted in an   
   >> error message. It did and the message was "Segmentation fault (core   
   >> dumped)".   
   >   
   > Does your SM create a crash report? I've been out of the loop too long   
   > and am not very knowledgeable about the most recent SM's or the Linux   
   > versions. The crash report may point to the segfault though it takes   
   > skill to figure out why. Same if there is a core file produced by the   
   > crash (probably not due to permissions) which can be attached to GDB   
   > and examined if you have the skill set. I don't have that skill.   
   > Dave   
      
   Both the core file and running seamonkey from inside gdb and make it   
   crash should allow you to obtain a backtrace ("bt full", I think), but   
   getting a more meaningful backtrace requires debugging symbols.   
      
   That's probably less of an issue for official builds from the SeaMonkey   
   project, but if your build is from another source (you built it or it   
   was packaged by your distribution), you'll need to get the debugging   
   symbols for that.   
      
   --   
   Nuno Silva   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)