Random *** stack smashing detected *** message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

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?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux