Exit codes with top bit set to 1 (IOW higher than 127) usually mean
unhandled signal. In your case 141 & 127 = 13 (or 141 - 128 = 13 if you
want) indicating the app got SIGPIPE and died on it.
This is not 100% reliable since you can deliberately exit your app with
>127 code but most apps do not
On 02.06.2015 o 12:19 Richard W.M. Jones wrote:
On Mon, Jun 01, 2015 at 10:10:17PM +0200, Michal Toman wrote:
Apart from mips64el, we have lately started working on 32-bit mipsel, to
be ran on the Creator CI20 Borad [4]. This is basically 3 months behind
mips64el so there are no significant
Greetings everyone,
you might know me from my former work on ABRT, or later Power and s390.
For the last few months however, I have been collaborating with
Imagination Technologies to bring back Fedora for MIPS.
A brief history - some effort to bootstrap Fedora for MIPS has been done
around
Hi everybody,
we have just replaced the old (and slow :)) host running Retrace Server
and ABRT server with a new one. The most significant changes for users are:
- Retracing now runs in memory, which means faster generating of
backtraces (by an order of magnitude)
- Reports from CentOS 7 are
On 06.12.2013 14:34, Ralf Corsepius wrote:
On 12/06/2013 02:14 PM, Jiri Moskovcak wrote:
On 12/06/2013 02:10 PM, Ralf Corsepius wrote:
On 12/06/2013 12:14 PM, Jóhann B. Guðmundsson wrote:
On 12/06/2013 09:56 AM, Jakub Filak wrote:
Hello,
I'd like to add abrt-cli package to the comps group
On 06.12.2013 14:51, Jóhann B. Guðmundsson wrote:
On 12/06/2013 01:47 PM, Lukas Zapletal wrote:
We all do fix the application for his mother, after it's reported by
ABRT or any other means:-)
No not really our distribution is filled with just packagers that dont
know what to do with those
In last two weeks these components were crashing the most:
1. kernel seen 85925 times (52% of all reports)
https://retrace.fedoraproject.org/faf/problems/1174076/
https://retrace.fedoraproject.org/faf/problems/1209703/
2. xulrunner seen 10191 times (6% of all reports)
Hot problems:
ID Components Count
---
185766 kernel 1294
204154 kernel 1198
85820 yumex786
Hot problems:
ID Components Count
---
34452 dconf450
28310 kernel 379
228274 kernel 327
Hot problems:
ID Components Count
---
186587 kernel 411
186872 kernel 350
185998 gnome-packagekit 212
Hi Dave!
We have started a similar project in ABRT some year ago. The original
purpose was to automatically determine some crash characteristics
(security impact, unchecked user input etc.). The overall idea is
rebuilding the given package with some compiler plugin and go through
the AST
Greetings everybody!
As you may have noticed, new ABRT 2.0.12 has recently been pushed to
Fedora. Besides significant changes in reporting workflow, it also uses
the ABRT server to collect what we call uReports (micro-reports).
uReport is a short (usually 4kB) fingerprint of the crash, with
On 05.09.2012 11:44, J. Randall Owens wrote:
On 09/05/2012 02:39 AM, Michal Toman wrote:
Greetings everybody!
As you may have noticed, new ABRT 2.0.12 has recently been pushed to
Fedora. . . .
F16, F17, F18, rawhide? Or just F18 rawhide? Or. . . ?
Ohh, sorry - F17, F18 Rawhide
M
Hi Neal,
this happens because retrace server uses yum and yum is not able to
fully resolve dependencies in some specific situations. In that case
there is no reason to continue because the resulting backtrace would be
unusable.
What package are you trying to retrace? AFAIK there seems to be a
Hi,
we have successfully launched the Retrace Server application on
retrace01.fedoraproject.org machine. The detailed description can be
found on Retrace Server's feature page:
http://fedoraproject.org/wiki/Features/RetraceServer. Feel free to try
it using temporary testing script, according
15 matches
Mail list logo
