Petr Mladek wrote
Create the wiki pages about getting the windows
backtrace.
Hi.
Draft is available at
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg.
LO Windows developers are asked to comment:
- what debug output do they actually need
- which additional WinDbg
Hi bfo,
I am sorry for the late replay. I had busy days.
On Mon, 2012-06-04 at 08:55 -0700, bfo wrote:
Petr Mladek wrote
Yes, any help is really appreciated. If you feel like, please propose
some prioritization.
From my users perspective the proposal is simple:
1. crashers
2.
On Mon, Jun 04, 2012 at 07:11:03PM +0200, Nino wrote:
I gave it a (first) try :)
Looking much better already. Thanks!
Best,
Bjoern
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
On Fri, 2012-06-01 at 13:10 -0700, bfo wrote:
Michael Meeks-2 wrote
I think it won't do any good in the long term. Enabling reporting tool would
give you a chance to
get more data without the need to know the bugzilla magic by the users (just
opt in to send the reports).
It could bring
Petr Mladek wrote
If you prepare the pages and template and
if it is easy to add new week, Michael might do it himself in the
future.
Firefox team is using CreateBox Wiki Extension for minutes - check their
wiki page at https://wiki.mozilla.org/Platform#Meetings
Yes, any help is
Hi Rainer,
On Mon, Jun 04, 2012 at 08:55:59AM -0700, bfo wrote:
I thought so, but according to http://wiki.documentfoundation.org/BugTriage
there are three bold ANDs before you can change a status to NEW.
Further more, an exclamation mark at the end of that paragraph
(and the whole scary
On 04.06.2012 18:02, Bjoern Michaelsen wrote:
On Mon, Jun 04, 2012 at 08:55:59AM -0700, bfo wrote:
I thought so, but according to http://wiki.documentfoundation.org/BugTriage
there are three bold ANDs before you can change a status to NEW.
Further more, an exclamation mark at the end of that
Bjoern Michaelsen wrote
Crash counter (search for libreoffice-core):
https://errors.ubuntu.com/
Open LibreOffice crasher bugs by most affected users:
Open LibreOffice crasher bugs by bug heat:
This s very cool. Question - why I have mostly page not find errors when I
click in the Bugs
On Mon, Jun 04, 2012 at 09:02:43AM -0700, bfo wrote:
Bjoern Michaelsen wrote
Crash counter (search for libreoffice-core):
https://errors.ubuntu.com/
Open LibreOffice crasher bugs by most affected users:
Open LibreOffice crasher bugs by bug heat:
This s very cool. Question -
Bjoern Michaelsen schrieb:
As Ubuntu, we do:
https://errors.ubuntu.com/
boaster ;-)
Hi,
yes, I think such automatted statistics can be a good indicator.
Best regards
Rainer
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
Michael Meeks-2 wrote
On Fri, 2012-05-25 at 11:35 -0700, bfo wrote:
I read that you have unused reporting tool in the codebase and plans
to bring it back to life. Without it do you know the top crashers?
Not really; we rely on human bug filing and QA to bring these to our
attention;
Hi,
On Fri, May 25, 2012 at 11:35:23AM -0700, bfo wrote:
I read that you have unused reporting tool in the codebase and plans
to bring it back to life. Without it do you know the top crashers?
As Ubuntu, we do:
Crash counter (search for libreoffice-core):
https://errors.ubuntu.com/
Open
bfo píše v Po 28. 05. 2012 v 08:37 -0700:
bfo wrote
As I wrote earlier I have pdb symbols and source links in the WinDbg
outputs,
but I am concerned about missing FAULTING_SOURCE_LINE and
FAULTING_SOURCE_CODE sections.
I managed to receive outputs with FAULTING_SOURCE_CODE
Hi there,
On Fri, 2012-05-25 at 11:35 -0700, bfo wrote:
I read that you have unused reporting tool in the codebase and plans
to bring it back to life. Without it do you know the top crashers?
Not really; we rely on human bug filing and QA to bring these to our
attention; of course,
bfo wrote
As I wrote earlier I have pdb symbols and source links in the WinDbg
outputs,
but I am concerned about missing FAULTING_SOURCE_LINE and
FAULTING_SOURCE_CODE sections.
I managed to receive outputs with FAULTING_SOURCE_CODE section just as in
Jesus screencast.
Hi bfo,
it is great that you continue working on it.
Please, do not remove people from CC. There is a lot of traffic on the
mailing list. The interested people might miss your replay :-)
bfo.bugm...@spamgourmet.com píše v Čt 24. 05. 2012 v 19:56 +0200:
I just read in ESC minutes that daily
Petr Mladek schrieb:
Norbert, would be possible to hack the tindebox script to upload also
the .pdb file?
https://bugs.freedesktop.org/show_bug.cgi?id=50339
I managed to get WinDbg to work
Me too, with build from tinderbox 20, but gives error message missing
symbols.
I will continue
bfo.bugm...@spamgourmet.com píše v Čt 24. 05. 2012 v 21:20 +0200:
On Wed, May 23, 2012 at 3:11 PM, Petr Mladek - pmla...@suse.cz wrote:
Please consider. Always you can ask the friendly guys at Mozilla how
to set this all up...
Thanks for tip.
What a discovery! Seems like complete how to:
On Fri, May 25, 2012 at 12:03 PM, Petr Mladek - pmla...@suse.cz wrote:
but I am not sure if my WinDbg output is any good.
It is probably less informative without the .pdb files. Anyway, I guess
that your are on the right way.
As I wrote earlier I have pdb symbols and source links in the WinDbg
On Fri, May 25, 2012 at 3:21 PM, Petr Mladek - pmla...@suse.cz wrote:
We are already using Litmus and are going to migrate to Moztrap. Though,
we are not familiar with the real processes that used in the Mozilla
project.
Do you have any experience with the Mozilla processes? Are you able to
On Wed, May 23, 2012 at 3:11 PM, Petr Mladek - pmla...@suse.cz wrote:
Please consider. Always you can ask the friendly guys at Mozilla how
to set this all up...
Thanks for tip.
What a discovery! Seems like complete how to:
bfo.bugm...@spamgourmet.com píše v Pá 18. 05. 2012 v 22:22 +0200:
On Thu, 2012-05-10 at 12:13 +0200, Jesús Corrius wrote:
In any case, the right way to do it would be to automatically generate
all PDBs for each released version, for example in: solver\wntmsci.pro\pdb.
Then we put those
On Thu, 2012-05-10 at 12:13 +0200, Jesús Corrius wrote:
In any case, the right way to do it would be to automatically generate
all PDBs for each released version, for example in: solver\wntmsci.pro\pdb.
Then we put those generated PDBs online at symbols.libreoffice.org.
I think first we should
On Wed, May 9, 2012 at 10:07 PM, Michael Meeks michael.me...@suse.com wrote:
Hi there,
Trying to get a good stack trace from vcl, I downloaded 3.5.3rc1 from:
http://dev-builds.libreoffice.org/win32-debug/libreoffice-3-5/
I get a beautiful crash in the MSVC++ debugger,
On Thu, 2012-05-10 at 12:13 +0200, Jesús Corrius wrote:
In any case, the right way to do it would be to automatically generate
all PDBs for each released version, for example in: solver\wntmsci.pro\pdb.
Then we put those generated PDBs online at symbols.libreoffice.org.
Right ! I
Then we put those generated PDBs online at symbols.libreoffice.org.
But is it documented how to set up such a symbol server? And would we
then need to bump the version numbers in the DLLs/EXEs in each and
every nightly build? Presumably the MS debuggers want to be quite sure
that some symbol
2012/5/10 Tor Lillqvist t...@iki.fi:
Then we put those generated PDBs online at symbols.libreoffice.org.
But is it documented how to set up such a symbol server? And would we
then need to bump the version numbers in the DLLs/EXEs in each and
every nightly build? Presumably the MS debuggers
On 10/05/12 13:13, Andras Timar wrote:
Using PDB files for release builds does not sound good to me, because
I don't think we should produce release builds with debug
configuration (i.e. no optimizations).
ah, another developer who doesn't know what our configure options do (or
are supposed
Hi there,
Trying to get a good stack trace from vcl, I downloaded 3.5.3rc1 from:
http://dev-builds.libreoffice.org/win32-debug/libreoffice-3-5/
I get a beautiful crash in the MSVC++ debugger, but no symbols; I try
to add vcllo.pdb from LOdev 3.5\program and it moans: The
29 matches
Mail list logo
