Red Hat Bugzilla – Bug 844129
crash with *** stack smashing detected ***
Last modified: 2016-11-30 19:30:54 EST
Created attachment 600998 [details]
Stack trace + Memory map
Description of problem:
k3b crashes with *** stack smashing detected ***
Version-Release number of selected component (if applicable):
Always (as normal user AND root)
Steps to Reproduce:
1. Run k3b
Stack trace + Memory map attached. Just ask if more is needed
Can you please provide valgrind log for k3b.
Run this command as user (not root):
valgrind --trace-children=yes k3b
And add result as an attachment here.
Valgrind output provided as requested.
Created attachment 601332 [details]
Valgrind k3b output
Sorry, I've forgot to ask you to install debuginfo package for k3b. You can do it by running (as root):
yum install --enablerepo=\*-debuginfo k3b-debuginfo
Then rerun the valgrind command. And the stack trace with debuginfo might be also useful.
Created attachment 601569 [details]
Valgrind output + stack trace
Unfortunately, Valgrind is not all that helpful in this case because this is an overflow on the stack, which Valgrind does not detect.
What the stack traces from Valgrind do tell us, though, is that the overflow is somewhere in K3b::Device::Device::checkFeatures() in k3bdevice.cpp near line 3033. (That line number is probably the end of the function, the overflow of course happens further up in the code.)
k3b used to work until a few weeks ago, when an update supposedly screwed it up. Since no k3b update has been issued recently, I reckon it must have been some linked library. I had a look at the yum log, but I could not identify any that is used by k3b. Brasero works fine...
Rebuilt from source and reinstalled, cannot replicate.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.