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
[Crash-catcher] ices in laughter to
by Numbers Rezac
Ll the following story against himself: "There was a person who, for a
long time, studied under me the grammar of Sibawaih, and who said to
me, when he got to the end of the book, 'May God requite you
well! As for me, I have not understood a letter of it.'" Yahya,
a celebrated preacher, on being
asked by a descendant of the Prophet, "Tell
me, Master! and may God assist you!
what is your opinion of us who are the people of the house,"--that is
to say, the members of Muhammad's family,--replied: "It is that which
I would say of clay kneaded with the water of divine revelation and
sprinkled with the water of
the heavenly mission: can it give out any other odour than the musk of
true direction and the
ambergris of piety?" The Alide was so highly pleased with this answer
that he filled Yahya's mouth with pearls. Yahya, who died on March 30,
872, had a very graceful turn for apophthegms. "True friendship," said
he, "cannot be augmented by kindness
nor diminished by unkindness." And again, he s
14 years, 1 month
[Crash-catcher] [PATCH] new backtrace rating algorithm
by Karel Klic
Hi,
the attached patches contains the new backtrace rating algorithm, and a
lot of changes triggered by this.
The patch should also improve duplicate detection, because it drops
additional details from the text that is used to compute the checksum.
It also marks some abrt core functions as extern "c", so we can start
compiling some code in ABRTUtils using gcc instead of g++.
And it identifies the crash function and stores its name to the dump dir.
Best regards,
Karel
14 years, 1 month
[Crash-catcher] Hts of matrimony, which the continent held
by Halaby Bagheri
See the
Tuillerie, And waddle through the Louvre." None of these, I believe,
however good and valid reasons in themselves, were the moving powers
upon the present occasion; the all-sufficient one being that Mrs.
Bingham had a daughter. Now Miss Bingham was Dublin too --but Dublin of
a later edition--and a finer, more hot-pressed copy than her mamma. She
had been educated at Mrs. Somebody's seminary in Mountjoy-square--had
been taught to dance by Montague--and had learned French from a Swiss
governess--with a number of similar advantages --a very pretty
figure--dark eyes--long
eye-lashes and a dimple--and last, but of course least, the deserved
reputation of a large fortune. She had made a most successful debut in
the Dublin world, where she was much admired and flattered, and which
soon suggested to her quick mind, as it has often done
in similar cases to a young provincial debutante, not to waste her
"fraicheur" upon the minor theatres,
but at once to appear upon the "great boards;" so far evidencing a
higher flight of imagination and enterprise than is usually found among
the clique of her early associates, who may be characterized as that
school of young ladies,
who like the "Corsair" and Dunleary, and say, "ah
don't!" She possessed much more common sense than her mamma,
and promised under proper
advantages to become speedily quite sufficiently acquainted with the
world and its habitudes. In the meanwhile, I perceived that she ran a
very considerable risque of being carried off by some mustachoed
Pole,
with a name like a sneeze, who
might pretend to enjoy
the entree into the fashionable circles of the continent. Very little
study of my two fair friends enabled me to see thus much; and
very little "usage" sufficed to render me speedily
intimate with
14 years, 1 month
[Crash-catcher] ABRT Meeting Summary 2010-03-32
by Denys Vlasenko
Future work on ABRT (ABRT v2?)
* Minimizing resource usage when idle.
- stop running abrtd daemon continuously.
- spawn ccpp hooks only when crash occurs.
- handle python crashes only when they occur.
- kernel oopses are detected by a small dedicated daemon
or even by a cron job.
- after crash data is dumped, a hook spawns
abrtd "not-exactly-daemon-now" for further processing
of the crash: more info collected, dbus signal emitted, etc.
- python hook can perform dbus call asking abrtd to *create*
the crash dump on its behalf, avoiding selinux problems.
This still doesn't need abrtd to run continuously,
dbus autostart helps here.
- abrtd, started by any of these methods, shound time out
and exit on timeout.
* Convert plugins to children.
- plugins communicate back to parent abrtd via messages over stdout
and by exit code.
- can run plugins under non-root.
- any resource leaks in plugins don't have long-lasting effects:
as soon as they exit, everything is freed.
- can easily run concurrent plugins without more difficult
multithreaded coding.
- crashes in plugins do not take abrtd down.
- abrtd no longer needs to link against a lot of libraries.
- plugins do not need to link against dbus libraries.
- avoid problems with library initialization.
- plugin executables may find new uses on their own
(557943 RFE: Manually report a bz through abrt).
* Request files and other user data from non-root helper.
- biggest problem is ccpp crash: hook is started by root,
there is no way to access ~/files if they are e.g.
on NFS4 volume or denied by selinux.
- may want to collect non-file based info ($DISPLAY value etc).
- abrtd needs to have a new dbus signal "hey, I have a crash,
does anyone have any additional data for me?".
- perhaps abrtd should try to collect this info itself,
and ask for help only if it didn't work
(how to avoid tripping over selinux?).
- GUI applet or an "agent" daemon running under user UID
(think about servers) can listen for such dbus signals
and respond with dbus calls "hey abrtd, I have
this additional data for that crash".
- find out whether this "agent" can utilize dbus autostart.
* Make it possible to run abrtd under user, not root.
- GUI applet may chose to not talk to system abrtd,
but instead start an abrtd under current user and talk to it.
- this is safer wrt security.
- perhaps some functions will still need to be done by system
abrtd (e.g. debuginfo download and caching).
* Gradually migrate code to C.
* Gradually migrate to common style:
if (function(param, param))
{ /* braces are preferred but optional for one-statement if */
body;
}
if (err) return; /* one-line ifs discouraged */
* Reorganize source tree into:
doc
examples
src
includes (a few files only, or even only one file abrt.h)
lib (foo.c + foo.h)
cli
gui
daemon
plugins
hooks
Near term
* Delete *Socket*.* and Firefox.* files.
* Save "ls -lR /proc/$PID" listing in the crash.
--
vda
14 years, 1 month
[Crash-catcher] ABRT Meeting Summary 2010-01-06
by Denys Vlasenko
Future work on ABRT (ABRT v2?)
* Minimizing resource usage when idle.
- stop running abrtd daemon continuously.
- spawn ccpp hooks only when crash occurs.
- handle python crashes only when they occur.
- kernel oopses are detected by a small dedicated daemon
or even by a cron job.
- after crash data is dumped, a hook spawns
abrtd "not-exactly-daemon-now" for further processing
of the crash: more info collected, dbus signal emitted, etc.
- python hook can perform dbus call asking abrtd to *create*
the crash dump on its behalf, avoiding selinux problems.
This still doesn't need abrtd to run continuously,
dbus autostart helps here.
- abrtd, started by any of these methods, shound time out
and exit on timeout.
* Convert plugins to children.
- plugins communicate back to parent abrtd via messages over stdout
and by exit code.
- can run plugins under non-root.
- any resource leaks in plugins don't have long-lasting effects:
as soon as they exit, everything is freed.
- can easily run concurrent plugins without more difficult
multithreaded coding.
- crashes in plugins do not take abrtd down.
- abrtd no longer needs to link against a lot of libraries.
- plugins do not need to link against dbus libraries.
- avoid problems with library initialization.
- plugin executables may find new uses on their own
(557943 RFE: Manually report a bz through abrt).
* Request files and other user data from non-root helper.
- biggest problem is ccpp crash: hook is started by root,
there is no way to access ~/files if they are e.g.
on NFS4 volume or denied by selinux.
- may want to collect non-file based info ($DISPLAY value etc).
- abrtd needs to have a new dbus signal "hey, I have a crash,
does anyone have any additional data for me?".
- perhaps abrtd should try to collect this info itself,
and ask for help only if it didn't work
(how to avoid tripping over selinux?).
- GUI applet or an "agent" daemon running under user UID
(think about servers) can listen for such dbus signals
and respond with dbus calls "hey abrtd, I have
this additional data for that crash".
- find out whether this "agent" can utilize dbus autostart.
* Make it possible to run abrtd under user, not root.
- GUI applet may chose to not talk to system abrtd,
but instead start an abrtd under current user and talk to it.
- this is safer wrt security.
- perhaps some functions will still need to be done by system
abrtd (e.g. debuginfo download and caching).
* Gradually migrate code to C.
* Gradually migrate to common style:
if (function(param, param))
{ /* braces are preferred but optional for one-statement if */
body;
}
if (err) return; /* one-line ifs discouraged */
* Reorganize source tree into:
doc
examples
src
includes (a few files only, or even only one file abrt.h)
lib (foo.c + foo.h)
cli
gui
daemon
plugins
hooks
Near term
* Delete *Socket*.* and Firefox.* files.
* Save "ls -lR /proc/$PID" listing in the crash.
--
vda
14 years, 1 month
