Qa should run backtraces for the dev team. The dev team can focus on
implementing the fixes. We should not ask end users to perform the traces.
If they are comfortable with doing it . Then this is great. As I was told
the wiki is for contributors and not end users.
Mas
On Sep 7, 2012 4:05 PM,
Hi Julien,
On Fri, 2012-09-07 at 14:47 -0700, julien2412 wrote:
First backtrace are very useful only if they contain symbols.
Well - not -entirely- true, some backtrace is better than nothing at
all, but to have much hope of going wrong we need a symbols trace - yes.
Why is that ?
Le 10/09/12 10:47, Michael Meeks a écrit :
Hi Michael,
And for Mac too please :-)
It always seems to me to be such a pointless exercise running gdb as
a QA member against daily builds that have no symbols.
Right; so I believe Norbert was/is going to tweak his tinderbox to
provide
On 09/07/2012 11:47 PM, julien2412 wrote:
Just to add my support for Julien's request :
But:
Main (all?) Linux distributions provide the LO symbols package so you don't
need to build LO to retrieve useful bt.
And for Mac too please :-)
It always seems to me to be such a pointless exercise
Hi John,
On Fri, 2012-09-07 at 19:10 +0200, John Smith wrote:
Maybe im just dumb, but: Once you have provided a reliable and
reproducible test case (in this case, download the odt file attached
to the report and save it as docx in libreoffice), is there still a
need to provide further info at
On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com wrote:
Hi John,
You can always make it easier for a developer to solve - and the
easier
it is, the more likely it is to get solved quickly. Ways to do that are:
* getting a stack-trace with full debugging
On Fri, Sep 7, 2012 at 10:44 AM, John Smith lbalba...@gmail.com wrote:
On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com
wrote:
Hi John,
You can always make it easier for a developer to solve - and the
easier
it is, the more likely it is to get solved
The best solution would be to have a debug symbol server, then there
would be easily accessible debug symbols even for the release builds.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
On Fri, Sep 7, 2012 at 9:42 PM, Joel Madero jmadero@gmail.com wrote:
Sounds good, but I agree with John that better instructions are needed. I'm
working on a new triage page and hopefully in there we can get someone to
contribute incredibly precise, easy for noobs, instructions for every
I'll bring this up at our next conference call and see if there is a
possible solution.
Best Regards,
Joel
On Fri, Sep 7, 2012 at 12:48 PM, John Smith lbalba...@gmail.com wrote:
On Fri, Sep 7, 2012 at 9:42 PM, Joel Madero jmadero@gmail.com wrote:
Sounds good, but I agree with John
On Fri, Sep 7, 2012 at 9:49 PM, Joel Madero jmadero@gmail.com wrote:
I'll bring this up at our next conference call and see if there is a
possible solution.
Best Regards,
Joel
May I humbly note that I personally feel that developers should be
able to produce their own backtraces, given
This isn't for end-users, it's for QA team..and it's our job to do as
much as possible to help the developers. I know when I'm doing the
development side I appreciate whatever previous info users and QA can
provide. It's maximizing the efficiency of our abilitieslimited # of
developers
On Fri, Sep 7, 2012 at 9:59 PM, Joel Madero jmadero@gmail.com wrote:
This isn't for end-users, it's for QA team..and it's our job to do as
much as possible to help the developers. I know when I'm doing the
development side I appreciate whatever previous info users and QA can
provide.
Just some thoughts here.
First backtrace are very useful only if they contain symbols.
It's more difficult to retrieve bt on Windows than on Linux (I don't know
how MacOs could be compared with them)
It seems no daily builds contain symbols or missed it
(http://dev-builds.libreoffice.org/daily/).
Hi All,
Came across this bug FDO#45570 and I've already nominated as a most
annoying bug but I think that devs might appreciate me getting some kind of
a log or something together for the crash. What type of log should I create
and how do I go about doing this (basic steps, my knowledge of
On Fri, Sep 7, 2012 at 6:11 PM, Joel Madero jmadero@gmail.com wrote:
Hi All,
Came across this bug FDO#45570 and I've already nominated as a most annoying
bug but I think that devs might appreciate me getting some kind of a log or
something together for the crash. What type of log should I
I don't see that helping much, as the developer who takes this one can
quickly do this themselves. A working doc only takes 2 seconds to make.
Best Regards,
Joel
On Fri, Sep 7, 2012 at 9:35 AM, John Smith lbalba...@gmail.com wrote:
On Fri, Sep 7, 2012 at 6:11 PM, Joel Madero
On Fri, Sep 7, 2012 at 6:38 PM, Joel Madero jmadero@gmail.com wrote:
I don't see that helping much, as the developer who takes this one can
quickly do this themselves. A working doc only takes 2 seconds to make.
Best Regards,
Joel
Another random thought then: Is there a way to reproduce
Wrong Bug, dammit, my bad. Here is the proper one, attachment is there and
functioning, I had 5 open FDO tabs in FF and picked the wrong one.
https://bugs.freedesktop.org/show_bug.cgi?id=48569
My apologies
Joel
On Fri, Sep 7, 2012 at 9:57 AM, John Smith lbalba...@gmail.com wrote:
On Fri, Sep
On Fri, Sep 7, 2012 at 6:59 PM, Joel Madero jmadero@gmail.com wrote:
Wrong Bug, dammit, my bad. Here is the proper one, attachment is there and
functioning, I had 5 open FDO tabs in FF and picked the wrong one.
https://bugs.freedesktop.org/show_bug.cgi?id=48569
My apologies
Joel
Maybe
Hi John,
On Fri, 2012-09-07 at 19:10 +0200, John Smith wrote:
Maybe im just dumb, but: Once you have provided a reliable and
reproducible test case (in this case, download the odt file attached
to the report and save it as docx in libreoffice), is there still a
need to provide further info at
On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com wrote:
Hi John,
You can always make it easier for a developer to solve - and the
easier
it is, the more likely it is to get solved quickly. Ways to do that are:
* getting a stack-trace with full debugging
On Fri, Sep 7, 2012 at 10:44 AM, John Smith lbalba...@gmail.com wrote:
On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com
wrote:
Hi John,
You can always make it easier for a developer to solve - and the
easier
it is, the more likely it is to get solved
The best solution would be to have a debug symbol server, then there
would be easily accessible debug symbols even for the release builds.
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings:
On Fri, Sep 7, 2012 at 9:42 PM, Joel Madero jmadero@gmail.com wrote:
Sounds good, but I agree with John that better instructions are needed. I'm
working on a new triage page and hopefully in there we can get someone to
contribute incredibly precise, easy for noobs, instructions for every
On Fri, Sep 7, 2012 at 9:49 PM, Joel Madero jmadero@gmail.com wrote:
I'll bring this up at our next conference call and see if there is a
possible solution.
Best Regards,
Joel
May I humbly note that I personally feel that developers should be
able to produce their own backtraces, given
This isn't for end-users, it's for QA team..and it's our job to do as
much as possible to help the developers. I know when I'm doing the
development side I appreciate whatever previous info users and QA can
provide. It's maximizing the efficiency of our abilitieslimited # of
developers
On Fri, Sep 7, 2012 at 9:59 PM, Joel Madero jmadero@gmail.com wrote:
This isn't for end-users, it's for QA team..and it's our job to do as
much as possible to help the developers. I know when I'm doing the
development side I appreciate whatever previous info users and QA can
provide.
28 matches
Mail list logo
