On Tue, Sep 13, 2016 at 03:49:15PM +0300, Vassilis Virvilis wrote:
> On 09/13/2016 03:38 PM, Carsten Schoenert wrote:
> > Hello Vassilis,
> > 
> > please append such reports on the bugreport. Offline working people are
> > unable to get such pastes.
> 
> ok attached. I didn't know it is considered bad practice. I saw it somewhere
> and looked cool.

All related information has to be gone into the bug reporting system. As
systems like etherpad oder paste.foo are heavely relaying on a online
service bug reports become useless if parts of the reports are not
reachable. 

> > BTW: You also mixed up a different version than the thread subject is
> > talking about ... it's importend to know which versions report are
> > talking about. The compiler and some flags are different than in
> > unstable.
> > 
> 
> All bug reports are on debian unstable/experimental. There are 3 different
> crashes and it wasn't feeling right to create 3 bug reports (I had already
> created one) when there is this bug report about random crashes. A cursory
> overview on this bug reveals many posted crashdumps. So I thought I could
> add 3 more here. I tried to see if they are the same but that was a lot of
> work actually since I am not familiar with thunderbird codebase.

You need a widther look ;), the original starting report was about issues
in stable-security. You talking about unstable/testing. This are since
the GCC6 switch completely different worlds. So it's mostly impratical
to try to compare booth releases. And we need a lot of time to jump
between different bug report about propably the same issue and
coordinate those with upstream reported bug reports.

We may know a bit more about the codebase of Icedove/Thunderbird, but we
are also fare away from a deep knowledge about to catch the segfaults.

Regards
Carsten

Reply via email to