Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date
All threads index page 1

Qt-interest Archive, May 2007
Re: Qt GUI limitations

• Subject: Re: Qt GUI limitations
• From: Dimitri <dimitri@xxxxxxxxxxxxx>
• Date: Tue, 01 May 2007 19:02:22 +0200
• Delivered-to: qt-interest@trolltech.com
• List-help: <mailto:qt-interest-request@trolltech.com?subject=help>
• List-post: <mailto:qt-interest@trolltech.com>
• List-subscribe: <mailto:qt-interest-request@trolltech.com?subject=subscribe>
• List-unsubscribe: <mailto:qt-interest-request@trolltech.com?subject=unsubscribe>
• Organization: Trolltech ASA
• Resent-from: qt-interest@xxxxxxxxxxxxx
• Resent-message-id: <s0BdjD.A._LG.lK3NGB@esparsett>
• Resent-sender: qt-interest-request@xxxxxxxxxxxxx
• To: qt-interest@xxxxxxxxxxxxx

Hi,

>> This sounds familiar: the glibc has a few detection routines that alert you 
>> if it thinks your memory management is corrupted. This could be one or 
>> multiple of:
>>
>>   
> Yes, if I set MALLOC_CHECK = x the message disappears, but leaves me 
> wondering if there is a deeper problem in my program,
> or a bug in Qt or glibc-2.5-10 (I'm developing on Fedora 6).

This indeed looks like a deeper problem in the program. Which exact version of 
QextSerial is this? Where did you get it from?

--
 [ signature omitted ]