On Tue, Feb 25, 2014 at 05:33:29PM +0000, J Chetwynd wrote: > it's not clear to me that this is icedove, however so far only icedove > consistently crashes wheezy.
We will see. > could you please send me specific instructions relating to my > problem**? I will try. :) > bearing in mind I am concerned at possibility of corrupting hard > drive. as with system crash I literally have to unplug to reboot. Not really, the linux filesystems are more tolerate to such things like the Windows NTFS. > **I read through: > https://wiki.debian.org/Icedove#Debugging > and found it confusing. Debugging is mostly for all "normal" users not easy. To get debugging informations you have to do some things you normaly never will do, we have hopefully collect all the needed things and steps written into the wikipage. But o.k. I will make it hopefully clear to you what you should do. > I read through and tried the hello exercise: > How to get a backtrace > > on wheezy I tried: > > icedove -g [-safe-mode] 2>&1 | tee /tmp/icedove-gdb-$(apt-cache show icedove > | grep Version | awk '{ print $2 }')_$(date +%F_%T).log > > before system crash iirc > -g was not recognised, You have read the line above this command line? This line is important! >> # use this if you are running Wheezy (stable) or Squeeze (oldstable) You are using Wheezy (and not Squeeze) o.k., but not the 'stable' tree. The stable packages for Icedove are from version 10! So o.k. what tree of Wheezy you are using? As you wrote you have installed Icedove with version 17.0.10, so you must use the 'stable-security' tree (that is the normal case). https://packages.debian.org/source/stable/icedove With this information you will asume that the command above is the wrong line. So you have simple to use the other command line, you have could find it out by yourself by just testing it too. > i also tried : > > $ gdb icedove -g [-safe-mode] 2>&1 | tee /tmp/icedove-gdb-$(apt-cache show > icedove | grep Version | awk '{ print $2 }')_$(date +%F_%T).log > > gdb: unrecognized option '-g' With this line you have tried to start the GNU Debugger 'gdb' with an unknown option for gdb. The gdb works in another way. Either you simply start the debugger (gdb) and starting then the application inside, or you have gdb to tell wich pid or remote host to take. The second line on the wiki uses a wrapper script from the mozilla sources that calls the gdb with needed arguments and starts then the gdb session. No further action have to be done by you. And please create a tarball of your logs! The output of the gdb will be hughe. For example do a $ tar Jcvf I_set_a_better_filename.tar.xz /path/to/logfile1 /path/to/logfile2 # and so on As the description in the example for the possible output of the gdb is a little bit misstakable I will rework the wiki side. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
