Re: Random *** stack smashing detected *** message

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

 



On Wed, Sep 05, 2018 at 06:40:47PM +0200, Mark Wielaard wrote:
> On Wed, Sep 05, 2018 at 04:30:59PM +0100, Richard W.M. Jones wrote:
> > On Wed, Sep 05, 2018 at 05:23:45PM +0200, Mark Wielaard wrote:
> > > On Wed, 2018-09-05 at 13:59 +0100, Richard W.M. Jones wrote:
> > > > On Wed, Sep 05, 2018 at 02:27:44PM +0200, Florian Weimer wrote:
> > > > > 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.
> > > > 
> > > > Oh I see, good point.  I only had debuginfo installed for the
> > > > new version.
> > > > 
> > > > I've now installed every debuginfo related to the coredump,
> > > > and the old glibc debuginfo, but still:
> > > > 
> > > > Thread 1 (Thread 0x7f13c7b7d740 (LWP 31373)):
> > > > #0  0x00007f13c71ce46f in ?? ()
> > > > #1  0x0000000000000000 in ?? ()
> > > > 
> > > > So, I don't know ...
> > > 
> > > You could try eu-stack, with -l it should print out a memory map which
> > > might give you a hint about the modules/build-ids.
> > > $ eu-stack -v -l -b -m --core core.file
> > 
> > It gives an odd error (see attached).  Is that a bug in eu-stack?
> 
> It just says it also cannot unwind the stack, the stack might
> just be corrupt, or because of the missing libraries it might not
> have enough information or a wrong view of what is mapped where.
> 
> But we do now know that the process is bash-4.4.23-2 running against
> the old, no longer installed, libc-2.27.9000.so.
> 
> We don't know the exact release version, but given the build-id
> [0aea4b30d53d7cc6386f1773a8dc8972793def1a] we should be able to
> match it against an older glibc package.

Would I expect some file or symlink matching
*0aea4b30d53d7cc6386f1773a8dc8972793def1a* to exist in the
filesystem, given I have what I think is the correct glibc debuginfo
to be installed?  Because it does *not* exist:

$ find /usr -name '*0aea4b30d53d7cc6386f1773a8dc8972793def1a*'
find: ‘/usr/share/polkit-1/rules.d’: Permission denied
find: ‘/usr/share/selinux/targeted/default/active’: Permission denied
find: ‘/usr/libexec/initscripts/legacy-actions/auditd’: Permission denied

Does this indicate that I have the wrong glibc debuginfo
installed?

$ rpm -q glibc-debuginfo
glibc-debuginfo-2.27.9000-35.fc29.x86_64
$ rpm -ql glibc-debuginfo | grep 0aea4b30d53d7cc
[no output]

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
_______________________________________________
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