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 1791 - Build issue: TQThreadInstance::start: Setting thread storage to 0x88c63f0
Summary: Build issue: TQThreadInstance::start: Setting thread storage to 0x88c63f0
Status: RESOLVED INVALID
Alias: None
Product: TDE
Classification: Unclassified
Component: qt3 (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2013-12-28 08:54 CST by Darrell
Modified: 2018-08-01 04:42 CDT (History)
3 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 Darrell 2013-12-28 08:54:49 CST 
After compiling TQt3 using -debug rather than -release, my xsession-error log is filled with instances of the following:

TQThreadInstance::start: Setting thread storage to 0x88c63f0
TQThreadInstance::finish: In TQThreadInstance::finish for thread 0x88c63f0

The messages are harmless but the messages bloat the log and as can be seen, are useless with respect to most users for debugging.

The messages are derived from (t)qt3/src/kernel/qthread_unix.cpp.

A sledge hammer approach would be to comment out those messages in the sources when compiling. Perhaps there is a more elegant solution to reduce the spew.
Comment 1 Michele Calgaro 2018-08-01 04:42:58 CDT 
When compiling with debug option enabled, it is to be expected to have additional messages.... Closing.