On Mon, 25 Jan 2016 19:16:33 +0100, Kevin Fenzi wrote:
> so you could well have an update that isn't the current one that has no
> debuginfo on mirrors, but you could always get it from koji.
If you have only a core file you know build-ids dumped there but not NVRAs.
build-id -> NVRA mapping was
On Mon, 25 Jan 2016 20:12:44 +0300
Roman Tsisyk wrote:
> One more question.
> How long debuginfo packages are stored in repositories?
> For example, someone may have an old version of package for which
> debuginfo already has gone. How to debug in this case?
They are kept just like any other sub
On Mon, 25 Jan 2016 18:12:44 +0100, Roman Tsisyk wrote:
> How long debuginfo packages are stored in repositories?
> For example, someone may have an old version of package for which debuginfo
> already has gone.
> How to debug in this case?
ABRT retrace server has some storage and infrastructure f
On Sat, Jan 23, 2016 at 08:12:06PM +0300, Roman Tsisyk wrote:
> > Thursday, January 14, 2016 10:03 AM -06:00 from Michael Catanzaro
> > :
> >
> >
> > 'coredumpctl gdb' is great and you will enjoy it!
> >
>
> I have problems with `coredump gdb` and `coredump dump` on rawhide:
>
> ```
> # cored
On 19/01/16 11:36, Jonathan Wakely wrote:
On 19/01/16 11:10 +, Tom Hughes wrote:
On 19/01/16 10:55, Jonathan Wakely wrote:
Is there a way to tell it to ignore certain core files?
I run parts of the GCC testsuite several times a day, and many of the
tests are expected to call abort() to te
On 19/01/16 12:32 +0100, Jakub Filak wrote:
On 01/19/2016 11:55 AM, Jonathan Wakely wrote:
On 19/01/16 11:00 +0100, Jakub Filak wrote:
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredu
Am 19.01.2016 um 12:36 schrieb Tom Hughes:
On 19/01/16 11:32, Jakub Filak wrote:
I cannot tell how it works in coredumpctl but ABRT C/C++ plugin can
be configured to ignore any path (this feature will be available in ABRT
2.8 [1]).
Right now, you can configure ABRT to drop core files of cert
On 19/01/16 11:10 +, Tom Hughes wrote:
On 19/01/16 10:55, Jonathan Wakely wrote:
Is there a way to tell it to ignore certain core files?
I run parts of the GCC testsuite several times a day, and many of the
tests are expected to call abort() to terminate. I don't want hundreds
of them clog
On 19/01/16 11:32, Jakub Filak wrote:
I cannot tell how it works in coredumpctl but ABRT C/C++ plugin can
be configured to ignore any path (this feature will be available in ABRT
2.8 [1]).
Right now, you can configure ABRT to drop core files of certain programs
by adding program path to the Bla
On 01/19/2016 11:55 AM, Jonathan Wakely wrote:
On 19/01/16 11:00 +0100, Jakub Filak wrote:
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredumpctl, just disable
abrt-ccpp.service and ena
On 19/01/16 10:55, Jonathan Wakely wrote:
Is there a way to tell it to ignore certain core files?
I run parts of the GCC testsuite several times a day, and many of the
tests are expected to call abort() to terminate. I don't want hundreds
of them clogging up my journal, or being stored in ABRT.
On 19/01/16 11:00 +0100, Jakub Filak wrote:
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredumpctl, just disable
abrt-ccpp.service and enable abrt-journal-core.service:
http://abrt.readthe
On 01/14/2016 07:37 AM, Roman Tsisyk wrote:
Hi,
Fedora enables hardened builds [1] by default.
This implies -fomit-frame-pointer -fstack-protector and -fPIE.
[1]: https://fedoraproject.org/wiki/Packaging:Guidelines#PIE
How it is supposed to be debugged by upstream developers?
It would be n
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredumpctl, just disable
abrt-ccpp.service and enable abrt-journal-core.service:
http://abrt.readthedocs.org/en/latest/examples.html#getting-core
On Thu, 14 Jan 2016 11:39:23 +0100, Roman Tsisyk wrote:
> -debuginfo should be for the same build version as a binary itself.
> Most users never install -debuginfo.
GDB instructs them they should:
$ gdb -q xvinfo
Reading symbols from xvinfo...Reading symbols from /root/xvinfo...(no debugging
symb
On 01/14/2016 07:37 AM, Roman Tsisyk wrote:
> Hi,
>
> Fedora enables hardened builds [1] by default.
> This implies -fomit-frame-pointer -fstack-protector and -fPIE.
>
> [1]: https://fedoraproject.org/wiki/Packaging:Guidelines#PIE
>
> How it is supposed to be debugged by upstream developers?
W
16 matches
Mail list logo
