By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1004 - KIntNumInput corrupts memory
Summary: KIntNumInput corrupts memory
Status: RESOLVED INVALID
Alias: None
Product: TDE
Classification: Unclassified
Component: tdelibs (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All Linux
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2012-05-18 12:43 CDT by Timothy Pearson
Modified: 2012-10-19 15:28 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Pearson 2012-05-18 12:43:31 CDT 
KIntNumInput can leak and corrupt memory.

Reproduction is simple: add a KIntNumInput to a .ui file (inside a TQGroupBox) and run Valgrind on the result.  There will be many accesses and writes outside allocated blocks.

Replacing the KIntNumInput with a TQSpinBox resolves the memory corruption problems, indicating a problem within KIntNumInput itself.
Comment 1 Timothy Pearson 2012-05-18 13:12:18 CDT 
This seems to have been caused by an inconsistent build environment.

If anyone else runs into weird crashes after editing a .ui file, run 'make clean && make', as this resolved the problem for me.