[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 162940] program crash and stop to work
From: Carlos Wanderkoke <cwanderkoke () gmail ! com>
Date: 2008-05-31 18:11:36
Message-ID: 20080531181136.462.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=162940
------- Additional Comments From cwanderkoke gmail com 2008-05-31 20:11 -------
Hi Joris,
Sorry, but unfortunatelly I did NOT save the backtrace.
This crash happened tonight (again), but unfortunately I did NOT save the
crash erro details. If you know a way that i can use to recover this error
message I can prompt do it and send the complete backtrace back to you.
I have already faced the same error message at least 5 times during the last
two weeks, but today I decided to try to report it. My idea was to suggest
if we can somehow create a esier way to report bug, maybe saving the error
messages internally and the user want to submitt this error for analysis we
could do it in a easy and transparent way. The concept was not to create a
thousands of error messages, but give a chance to the end user save the bug
and if it does happen again the user will be able to send to the developers
team the complete error in details.
Many thanks for your prompt reply and support.
Best regards,
Carlos
2008/5/31 Joris Guisson <joris.guisson gmail com>:
[bugs.kde.org quoted mail]
Hi Joris,<br><br>Sorry, but unfortunatelly I did NOT save the backtrace.<br><br>This \
crash happened tonight (again), but unfortunately I did NOT save the crash erro \
details. If you know a way that i can use to recover this error message I can prompt \
do it and send the complete backtrace back to you.<br> <br>I have already faced the \
same error message at least 5 times during the last two weeks, but today I decided to \
try to report it. My idea was to suggest if we can somehow create a esier way to \
report bug, maybe saving the error messages internally and the user want to submitt \
this error for analysis we could do it in a easy and transparent way. The concept was \
not to create a thousands of error messages, but give a chance to the end user save \
the bug and if it does happen again the user will be able to send to the developers \
team the complete error in details.<br> <br>Many thanks for your prompt reply and \
support.<br><br>Best regards,<br><br>Carlos<br><br><br><div \
class="gmail_quote">2008/5/31 Joris Guisson <<a href="mailto:joris.guisson gmail \
com">joris guisson gmail com</a>>:<br> <blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;">------- You are receiving this mail because: -------<br> You \
reported the bug, or are watching the reporter.<br> <br>
<a href="http://bugs.kde.org/show_bug.cgi?id=162940" \
target="_blank">http://bugs.kde.org/show_bug.cgi?id=162940</a><br> <br>
<br>
<br>
<br>
------- Additional Comments From joris.guisson gmail com 2008-05-31 12:19 \
-------<br> You mean automatic reporting of crashes ? I can see where this is going \
to lead, umpteen duplicate reports about the same crash with a useless backtrace \
(most people don't have debug information installed), and most of the time said \
crash will probably be already fixed in a newer version. Which makes such a system a \
big waste of time for us developers.<br>
<br>
<br>
Anyway, when does this crash happen ? Have you got a backtrace ? Have you tried the \
3.0.2 release ?<br> </blockquote></div><br><br clear="all"><br>-- <br>Carlos \
Wanderkoke<br>Mob. + 55 21 8814-4622
[prev in list] [next in list] [prev in thread] [next in thread]