| 1 |
On Thu, 18 Apr 2019 10:14:13 -0400 |
| 2 |
John Covici <covici@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Thu, 18 Apr 2019 03:20:25 -0400, |
| 5 |
> Neil Bothwick wrote: |
| 6 |
> > |
| 7 |
> > [1 <text/plain; US-ASCII (quoted-printable)>] |
| 8 |
> > On Wed, 17 Apr 2019 21:41:41 -0400, John Covici wrote: |
| 9 |
> > |
| 10 |
> > > Apr 17 18:39:55 ccs.covici.com systemd-coredump[5334]: Process |
| 11 |
> > > 5332 (umount.davfs) of user 0 dumped core. |
| 12 |
> > > Apr 17 18:39:55 ccs.covici.com systemd[1]: |
| 13 |
> > > systemd-coredump@××××××××.service: Succeeded. |
| 14 |
> > > |
| 15 |
> > > I can't find that coredump, not sure if the process is allowed to |
| 16 |
> > > do it. |
| 17 |
> > |
| 18 |
> > From the systemd-coredump man page: |
| 19 |
> > |
| 20 |
> > By default, systemd-coredump will log the core dump including a |
| 21 |
> > backtrace if possible to the journal and store the core dump itself |
| 22 |
> > in an external file in /var/lib/systemd/coredump. |
| 23 |
> > |
| 24 |
> > You can change this in /etc/systemd/coredump.conf |
| 25 |
> |
| 26 |
> Thanks, I found it, but the backtrace has no symbols, even though I |
| 27 |
> have features set so that everything is compiled with symbols like |
| 28 |
> this: |
| 29 |
> FEATURES="${FEATURES} -stricter -distcc -ccache splitdebug buildpkg" |
| 30 |
> I wonder what is happening here? |
| 31 |
> |
| 32 |
> Strange thing si I have seen nothing on bgo for this problem. |
| 33 |
> |
| 34 |
|
| 35 |
I have the same problem on one of my machines. It segfaults somewhere |
| 36 |
in strcmp with avx2 according to a backtrace. |
| 37 |
Will try rebuilding my system libraries, since I changed lately from |
| 38 |
"march=native" to "march=x86-64 mtune=generic". I thought I rebuilt |
| 39 |
everything but there might be something missing for me. |
| 40 |
Anyway, for me as a workaround this works: fusermount -u MOUNTPOINT |
| 41 |
|
| 42 |
Cheers |
| 43 |
Andreas |
Archives