| 1 |
On Thu, 18 Apr 2019 03:20:25 -0400, |
| 2 |
Neil Bothwick wrote: |
| 3 |
> |
| 4 |
> [1 <text/plain; US-ASCII (quoted-printable)>] |
| 5 |
> On Wed, 17 Apr 2019 21:41:41 -0400, John Covici wrote: |
| 6 |
> |
| 7 |
> > Apr 17 18:39:55 ccs.covici.com systemd-coredump[5334]: Process 5332 |
| 8 |
> > (umount.davfs) of user 0 dumped core. |
| 9 |
> > Apr 17 18:39:55 ccs.covici.com systemd[1]: |
| 10 |
> > systemd-coredump@××××××××.service: Succeeded. |
| 11 |
> > |
| 12 |
> > I can't find that coredump, not sure if the process is allowed to do |
| 13 |
> > it. |
| 14 |
> |
| 15 |
> From the systemd-coredump man page: |
| 16 |
> |
| 17 |
> By default, systemd-coredump will log the core dump including a backtrace |
| 18 |
> if possible to the journal and store the core dump itself in an external |
| 19 |
> file in /var/lib/systemd/coredump. |
| 20 |
> |
| 21 |
> You can change this in /etc/systemd/coredump.conf |
| 22 |
|
| 23 |
Thanks, I found it, but the backtrace has no symbols, even though I |
| 24 |
have features set so that everything is compiled with symbols like |
| 25 |
this: |
| 26 |
FEATURES="${FEATURES} -stricter -distcc -ccache splitdebug buildpkg" |
| 27 |
I wonder what is happening here? |
| 28 |
|
| 29 |
Strange thing si I have seen nothing on bgo for this problem. |
| 30 |
|
| 31 |
-- |
| 32 |
Your life is like a penny. You're going to lose it. The question is: |
| 33 |
How do |
| 34 |
you spend it? |
| 35 |
|
| 36 |
John Covici wb2una |
| 37 |
covici@××××××××××.com |
Archives