On Tue, Sep 08, 2015 at 02:34:57AM +0530, shirish शिरीष wrote: > I definitely have icedove-dbg. > > $ dpkg -l icedove-dbg > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture > Description > +++-===============================-====================-====================-==================================================================== > ii icedove-dbg 40.0~b1-1 amd64 > Debug Symbols for Icedove
O.k., then there must be something going wrong. I can't find any relation to a segfault within your log. This look more like a log of a running application. > I am/was under the impression that just running gdb will do the needful. > > https://wiki.debian.org/HowToGetABacktrace This wiki site helds a lot of usfull additional information, but just one small step away there is also the wiki site for Icedove and there is a detailed explanation how to create a gdb log that is usfull for us. https://wiki.debian.org/Icedove#Starting_Debugging I thought you know this ... as this is not your first report. > The only difference is that I forgot to set the pagination bit, could > that be the reason or something else ? No, if you use the correct command line to call gdb there is normally no need for this, it's just set automatically pagination to off. > > Please note there are a few other bug reports there Icedove is crashing > > without any specific info why this is happen. they all need to connect > > to each other. > > Please guide so I can be more useful to you. Please read the Debian wiki page, there are other information like logging of mail server communication. Often you need to do multiple log actions. If the log is getting bigger please compress the files before sending. If the log doesn't contain a segault then think twice before sending it, for us such logs are useless. And iff the log is getting more complex please point us to the relevant parts, this save times to read the whole log file(s). Readjust of such logs and invastigation is very costly and take a lot of time and if we can't provoke the behaviour from your installation we can not fix the real problem. As Christoph and myself not really experts in reading gdb logs we need help from other persons, happily Guido is helping here. But then we need all the information in a correct shape. Sadly we only got rarly time for doing such audits. Regards Carsten
