Re: [Crash-catcher] java reports by crash catcher
by Michal Nowak
----- "Mark Wielaard" <mjw(a)redhat.com> wrote:
> Hi,
>
> It would be nice if crash-catcher could be thought about the
> hs_pid*.log
> files that a crashed java process creates. That file contains much
> more
> information that is relevant to the crash than the gdb backtrace that
> is
> currently collected. If it can see if there is a hs_pid###.log file
> (where ### is the process id of the java process that crashed) and
> attached that to the bug report it files that would be appreciated.
>
I am afraid Java exceptions are not supported at the moment (just the
python ones) and thus ABRT is not being run in such cases.
Do you have some example crash, where ABRT stepped in?
Since Java apps exception handling is completely missing, perhaps
some of you guys can help?
> Thanks,
>
> Mark
Michal
>
> _______________________________________________
> Crash-catcher mailing list
> Crash-catcher(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/crash-catcher
13 years, 6 months
Re: [Crash-catcher] [PATCH] crude attempt to make it possible to see log in GUI. Please try.
by Michal Nowak
----- "Denys Vlasenko" <dvlasenk(a)redhat.com> wrote:
> On Tue, 2009-12-08 at 03:10 -0500, Michal Nowak wrote:
> > ----- "Jiri Moskovcak" <jmoskovc(a)redhat.com> wrote:
> >
> > > On 12/04/2009 06:16 PM, Denys Vlasenko wrote:
> > > > Basically, I am making "label" act as a multi-line
> > > > text field with all log lines, not the storage
> > > > for only the last line.
> > > >
> > >
> > > I would rather use some textview and make it into separate log
> window.
> > > I
> > > think the label shouldn't be used that way.
> >
> > Don't use separate window just for log, please. Make it more
> > accessible and place some text area withing ExpandBar (in SWT
> > speak [1]) in window w/ progress bar.
> >
> > [1]
> http://archive.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/new...
> > (the most background one)
>
> Why?
Every other window is disturbing for me. Don't want it to copy
old versions of PackageKit (v0.3 or so), where nearly every action
invoked new window.
What I'd like to see is the same window w/ progress bar we have now
+ ExpandBar, which hides/shows the text area w/ log.
If you wanna save the log per bt generation and show again later
from ABRT's main window via button, sounds good.
> --
> vda
>
>
> _______________________________________________
> Crash-catcher mailing list
> Crash-catcher(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/crash-catcher
14 years, 4 months
Re: [Crash-catcher] [PATCH] crude attempt to make it possible to see log in GUI. Please try.
by Michal Nowak
----- "Jiri Moskovcak" <jmoskovc(a)redhat.com> wrote:
> On 12/04/2009 06:16 PM, Denys Vlasenko wrote:
> > Basically, I am making "label" act as a multi-line
> > text field with all log lines, not the storage
> > for only the last line.
> >
>
> I would rather use some textview and make it into separate log window.
> I
> think the label shouldn't be used that way.
Don't use separate window just for log, please. Make it more
accessible and place some text area withing ExpandBar (in SWT
speak [1]) in window w/ progress bar.
[1] http://archive.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/new...
(the most background one)
> > I think I need to add a close button there,
> > and need to hide the progress bar when it's not needed.
> > Maybe even get rid of it, log lines provide more realistic
> > indication that we have some progress (or haven't!)
> >
>
> Progress bar was request from users so I wouldn't remove it.
>
> > Also, maybe need to create one window per report,
> > so that different reports do not mix log windows
> > into one?
> >
>
> Good idea, I think we can use the job id to identify the messages for
>
> different windows.
>
> > For now, I tried to just disable hide ops in the source.
> > Does not look too nice when I run it, but demonstrates
> > the idea.
> >
> > Perhaps we do need to hide it on success, but need to save
> > the log and add another button [Log] to the appearing
> > report window, to make it possible for user
> > to resurrect the log window and see the log text again.
> >
>
> Definitely hide on succes.
>
> > On error, we do not hide it, but let user see the log.
> > This is basically the motivation behind this patch -
> > if error happens, currently user sees only last line -
> > NOT useful in many cases.
> >
>
> I would just show some exclamation mark in the progress window with
> some
> text saying: "there were some problems generating the backtrace, click
>
> here to see the details".
>
> > Please try the patch, feel free to make it usable.
> > --
> > vda
> >
>
>
> _______________________________________________
> Crash-catcher mailing list
> Crash-catcher(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/crash-catcher
14 years, 4 months
[Crash-catcher] [PATCH] crude attempt to make it possible to see log in GUI. Please try.
by Denys Vlasenko
Basically, I am making "label" act as a multi-line
text field with all log lines, not the storage
for only the last line.
I think I need to add a close button there,
and need to hide the progress bar when it's not needed.
Maybe even get rid of it, log lines provide more realistic
indication that we have some progress (or haven't!)
Also, maybe need to create one window per report,
so that different reports do not mix log windows
into one?
For now, I tried to just disable hide ops in the source.
Does not look too nice when I run it, but demonstrates
the idea.
Perhaps we do need to hide it on success, but need to save
the log and add another button [Log] to the appearing
report window, to make it possible for user
to resurrect the log window and see the log text again.
On error, we do not hide it, but let user see the log.
This is basically the motivation behind this patch -
if error happens, currently user sees only last line -
NOT useful in many cases.
Please try the patch, feel free to make it usable.
--
vda
14 years, 4 months
[Crash-catcher] Query regarding ABRT's duplicate stack detection
by Nikhil Teletia
Hi
I have few questions regarding ABRT's duplicate stack detection
algorithm. On ABRT's plans page, it is mentioned that -
How to decide if 2 backtraces are the same or not?
calculate a hash from a "parsed" backtrace
My questions are -
1. What all informations are parsed from a backtrace ? is it only
list of function name or some other informations as well ?
2. If a backtrace has multiple threads, what kind of ordering is
performed before creating a hash? Two different crashes may have
similar threads but in backtrace threads might be jumbled up ?
Thanks in advance.
-Nikhil
14 years, 4 months
[Crash-catcher] notes from yesterday talk with Denys
by Jiri Moskovcak
Planned steps:
* make kerneloops plugin into separate daemon (convert it to a hook
and get rid of "cron plugins" which are wrong idea since the begining)
- and make it to the service (write an initscript)
* make C/C++ hook to be started by init script
- init scritp would run ccpp-hook --init whic shoudl just set the
core_pattern, which is now done by the C analyzer plugin
* simplify abrt.conf:
- move all plugin related info to plugins/<plugin>.conf
- enabled, action association, etc ...
- make abrtd to parse plugins/*.conf and set the config options
that it understand
- this will fix the case when this is in abrt.conf
[Cron]
KerneloopsScanner = 120
because this should be in plugins/kerneloops.conf
and thus shouldn't exist if kerneloops-addon is
not installed
I've updated the DESIGN doc in git. If you have some otehr comment/ideas
then don't hesitate to share :)
Thanks,
Jirka
14 years, 4 months
Re: [Crash-catcher] ABRT reporting bugs for foreign packages
by Michal Nowak
----- "Radek Vokál" <rvokal(a)redhat.com> wrote:
> On 11/30/2009 07:18 PM, Jiri Moskovcak wrote:
> > Our default config has "OpenGPGCheck = no" so it's possible to
> report
> > bugs in non-Fedora packages.
> >
> > See: https://bugzilla.redhat.com/show_bug.cgi?id=542287
> >
> > 1. we should enable it in stable release (F12)
> > 2. we should find another way how to determine if package comes from
> > koji and belongs to Fedora, because users can easily disable gpg
> checking
> >
> > Jirka
> >
>
> Can't you use vendor from the rpm header?
>
> Radek
That would also be a one step further in having multiple Bugzilla
accounts in ABRT and being able to report to Fedora's and RPM
Fusion's Bugzilla w/o settings change.
Michal
14 years, 5 months