On 09/05/2018 02:22 PM, Richard W.M. Jones wrote:
On Wed, Sep 05, 2018 at 02:10:15PM +0200, Florian Weimer wrote:
On 09/05/2018 02:07 PM, Richard W.M. Jones wrote:
I just hit a weird bug. When I typed:
$ sudo dnf update --best /mnt<tab>sc<tab>
bash exited (and with it, my ssh session) saying:
*** stack smashing detected ***: <unknown> terminated
Connection to srv closed.
This was after updating to glibc-2.28-9.fc29.x86_64.
Unfortunately I cannot seem to reproduce it on demand.
That looks rather unusual. From which version did you update?
I think from glibc 2.27.9000-35.fc29 -> 2.28-9.fc29.
There might have been an ld.so ABI change, so processes launched with
the old ld.so might file when they dlopen something which depends on the
new libpthread, for example.
The good news is that a coredump was collected. The bad news is
it looks pretty useless:
Thread 1 (Thread 0x7f13c7b7d740 (LWP 31373)):
#0 0x00007f13c71ce46f in ?? ()
#1 0x0000000000000000 in ?? ()
Before I file a bug, what component should be used? What other
information is useful? Why would this happen just from keyboard
input?
Please try get a backtrace with debuginfo installed. Thanks.
Yeah unfortunately that is with debuginfo :-(
But which one? For 2.28-9.fc29 or 2.27.9000-35.fc29? If GDB can't find
the build ID, I'd suggest try the other version as well.
Thanks,
Florian
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
