In-line :-
On 9/8/15, Carsten Schoenert <c.schoen...@t-online.de> wrote:
> 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.
Hi Carsten,
Sorry for being a nuisance. Didn't mean to be. I actually had another
session running and this is what it showed (again) . I do have it's
backtrace but am hesitant.
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7fffdeafe700 (LWP 3383)]
0x00007ffff7bcdd8f in __libc_send (fd=68,
buf=buf@entry=0x7fffbcf46000, n=n@entry=53, flags=flags@entry=0) at
../sysdeps/unix/sysv/linux/x86_64/send.c:31
31 ../sysdeps/unix/sysv/linux/x86_64/send.c: No such file or directory.
This surely means that the program (Broken pipe) bit.
<snipped>
Anyways, will get back to you will the file. I'm sorry it will be big
as I'm also not an expert in reading gdb files.
> Regards
> Carsten
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
