NoOp wrote:
On 03/17/2009 06:15 PM, Phillip Pi wrote:
On 3/17/2009 3:46 PM PT, Jens Hatlak wrote:
Ant wrote:
(no debugging symbols found)
(gdb)
Now what? I don't know how to use this gdb thing. :(
I don't know much more there either but the next step should be entering
"run". Then, for crash bugs, the next command after that would be "bt"
for getting a backtrace. Since in your case SM freezes I don't know
whether killing SM will give you similar results but you may try
pressing Ctrl+C in the console window instead of killing SM by other
means. Anyway, as the "(no debugging symbols found)" indicates, your SM
is stripped so you probably won't get meaningful results anyway. You'd
have to use a version compiled with debugging support but I'm not sure
whether those are available or you need to compile yourself. If you
installed SM using packages for your distribution it may be worth a try
to search for a matching package providing debugging symbols.
Thanks. Yeah, I can't find any Debian packages for SeaMonkey and Debian
dropped IceApe that is another name for SeaMonkey.
Oh well. I think my next plan is to try a new profile. Does anyone know
how to launch that under Linux like in Windows?
$ ./seamonkey -P
[mind the caps]
You can also do the same from your running SeaMonkey: Tools|Switch Profiles
You can also rename your .mozilla folder to something else temporarily,
then run seamonkey and it will create a new one. After you test you can
switch back.
In Ubuntu, adding the -ProfileManager switch to the shortcut that
launches SeaMonkey will bring up Profile Manager, exactly as on Windows,
I think your first advice is best, use Tools>>Switch Profiles.
Lee
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
