Bug 336833 - [Valgrind] "Invalid read of size 4" in KCrash::setCrashHandler(void (*)(int)) (qstring.h:89)
Summary: [Valgrind] "Invalid read of size 4" in KCrash::setCrashHandler(void (*)(int))...
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kcrash
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-28 15:56 UTC by Elias Probst
Modified: 2022-11-19 05:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elias Probst 2014-06-28 15:56:35 UTC
Ran into some memory issues with plasmashell and decided to run it in Valgrind, when I found this in my Valgrind results:

==511== Invalid read of size 4
==511==    at 0x5C178E0: KCrash::setCrashHandler(void (*)(int)) (qstring.h:89)
==511==    by 0x5C1864B: KCrash::setDrKonqiEnabled(bool) (kcrash.cpp:227)
==511==    by 0x5C18D22: kcrashInitialize() (kcrash.cpp:107)
==511==    by 0xB1C210F: QCoreApplication::init() (qcoreapplication.cpp:280)
==511==    by 0xB1C22B5: QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) (qcoreapplication.cpp:657)
==511==    by 0xA91BDC8: QGuiApplication::QGuiApplication(QGuiApplicationPrivate&) (qguiapplication.cpp:554)
==511==    by 0xA171DBC: QApplication::QApplication(int&, char**, int) (qapplication.cpp:563)
==511==    by 0x432E58: main (main.cpp:51)
==511==  Address 0x18aa57a0 is 0 bytes inside a block of size 3 alloc'd
==511==    at 0x4C2C5DB: malloc (vg_replace_malloc.c:270)
==511==    by 0x5C17879: KCrash::setCrashHandler(void (*)(int)) (kcrash.cpp:252)
==511==    by 0x5C1864B: KCrash::setDrKonqiEnabled(bool) (kcrash.cpp:227)
==511==    by 0x5C18D22: kcrashInitialize() (kcrash.cpp:107)
==511==    by 0xB1C210F: QCoreApplication::init() (qcoreapplication.cpp:280)
==511==    by 0xB1C22B5: QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) (qcoreapplication.cpp:657)
==511==    by 0xA91BDC8: QGuiApplication::QGuiApplication(QGuiApplicationPrivate&) (qguiapplication.cpp:554)
==511==    by 0xA171DBC: QApplication::QApplication(int&, char**, int) (qapplication.cpp:563)
==511==    by 0x432E58: main (main.cpp:51)

Built with gcc-4.8.2, running on Kernel 3.15.1 and glibc-2.17 and Qt 5.3.1
Comment 1 David Faure 2016-04-30 08:45:34 UTC
Does this still happen? When I valgrind the test program from kcrash (which also ends up in kcrashInitialize()), valgrind doesn't complain.

64 bit system, not 32 bits, right?
Comment 2 David Faure 2016-04-30 08:50:11 UTC
Ah, what is (was) the contents of your $DISPLAY environment variable?
Comment 3 Justin Zobel 2022-10-20 23:54:26 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-11-04 05:07:02 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-11-19 05:14:30 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!