Qt-interest Archive, August 2006
Program to big?
Pages: Prev | 1 | 2 | Next
Message 1 in thread
When I compile my program on Windows in debug mode (shared lib), it runs
fine. But when I make the release version (with staticlib), a DOS window
appears and flashes the message ³Program too big to fit in memory² and then
immediately quits.
How do I fix this? (I could find nothing in the FAQ or KnowledgeBase.
Qt version 4.1.4 commercial
Windows 2000 Service Pack 4 (via Terminal Services)
3GB RAM
Using Visual Studio 2003 .NET, latest patches
Does the same thing if I copy my program to a Windows XP Pro machine.
Keith Esau
Message 2 in thread
On 8/1/06, Keith Esau <keith.esau@xxxxxxx> wrote:
>
> When I compile my program on Windows in debug mode (shared lib), it runs
> fine. But when I make the release version (with staticlib), a DOS window
> appears and flashes the message "Program too big to fit in memory" and then
> immediately quits.
>
> How do I fix this? (I could find nothing in the FAQ or KnowledgeBase.
>
> Qt version 4.1.4 commercial
> Windows 2000 Service Pack 4 (via Terminal Services)
> 3GB RAM
> Using Visual Studio 2003 .NET, latest patches
>
> Does the same thing if I copy my program to a Windows XP Pro machine.
>
> Keith Esau
>
Keith,
That rings a bell. Are you loading something really big on the stack? For
example, did you statically allocate a big array globally, or in your
main()?
Regards,
Glen.
Message 3 in thread
There is more global data in the debug version than the release version, so
that shouldn¹t be the problem.
Keith
On 08-01-2006 4:27 PM, "Glen van de Mosselaer" wrote:
> On 8/1/06, Keith Esau <keith.esau@xxxxxxx> wrote:
>> When I compile my program on Windows in debug mode (shared lib), it runs
>> fine. But when I make the release version (with staticlib), a DOS window
>> appears and flashes the message "Program too big to fit in memory" and then
>> immediately quits.
>>
>> How do I fix this? (I could find nothing in the FAQ or KnowledgeBase.
>>
>> Qt version 4.1.4 commercial
>> Windows 2000 Service Pack 4 (via Terminal Services)
>> 3GB RAM
>> Using Visual Studio 2003 .NET, latest patches
>>
>> Does the same thing if I copy my program to a Windows XP Pro machine.
>>
>> Keith Esau
>
>
> Keith,
>
> That rings a bell. Are you loading something really big on the stack? For
> example, did you statically allocate a big array globally, or in your main()?
>
>
> Regards,
> Glen.
>
Message 4 in thread
Keith,
Never mind. A quick Google on the error message reveals that this is usually
a corrupt program header. Or that you're not actually compiling to an
executable format.
http://blogs.msdn.com/oldnewthing/archive/2006/01/30/519388.aspx
(this is a great blog, BTW)
Bad linker parameters in the Release profile? Bad "General: Project
Default"? I'd guess it's something in the Project properties. A corrupt
static Qt library, possibly? What happens if you build Release with Qt as a
DLL?
Glen.
On 8/1/06, Keith Esau <keith.esau@xxxxxxx> wrote:
>
> There is more global data in the debug version than the release version,
> so that shouldn't be the problem.
>
> Keith
>
>
> On 08-01-2006 4:27 PM, "Glen van de Mosselaer" wrote:
>
> On 8/1/06, *Keith Esau* <keith.esau@xxxxxxx> wrote:
>
> When I compile my program on Windows in debug mode (shared lib), it runs
> fine. But when I make the release version (with staticlib), a DOS window
> appears and flashes the message "Program too big to fit in memory" and then
> immediately quits.
>
> How do I fix this? (I could find nothing in the FAQ or KnowledgeBase.
>
> Qt version 4.1.4 commercial
> Windows 2000 Service Pack 4 (via Terminal Services)
> 3GB RAM
> Using Visual Studio 2003 .NET, latest patches
>
> Does the same thing if I copy my program to a Windows XP Pro machine.
>
> Keith Esau
>
>
>
> Keith,
>
> That rings a bell. Are you loading something really big on the stack? For
> example, did you statically allocate a big array globally, or in your
> main()?
>
>
> Regards,
> Glen.
>
>
Message 5 in thread
We do not want the release version to require Qt DLLs. If it doesn't work as
static for the release version, Qt is useless. The only reason the debug
version uses DLLs is for speed in the development process.
BTW, the application size is over 10MB. (Only 8.4MB on the debug version
that uses DLLs.)
So, I am still stuck at the same place. I am a Mac/Unix geek, so I really on
Qt to get the Windows settings correct. It appears some Windows 'header'
info is incorrect, but what do I do in Qt to fix it?
Keith
On 08-01-2006 5:56 PM, "Glen van de Mosselaer" wrote:
> Keith,
>
> Never mind. A quick Google on the error message reveals that this is usually a
> corrupt program header. Or that you're not actually compiling to an executable
> format.
>
> http://blogs.msdn.com/oldnewthing/archive/2006/01/30/519388.aspx
> (this is a great blog, BTW)
>
> Bad linker parameters in the Release profile? Bad "General: Project Default"?
> I'd guess it's something in the Project properties. A corrupt static Qt
> library, possibly? What happens if you build Release with Qt as a DLL?
>
>
> Glen.
>
> On 8/1/06, Keith Esau <keith.esau@xxxxxxx> wrote:
>> There is more global data in the debug version than the release version, so
>> that shouldn't be the problem.
>>
>> Keith
>>
>>
>> On 08-01-2006 4:27 PM, "Glen van de Mosselaer" wrote:
>>
>>> On 8/1/06, Keith Esau < keith.esau@xxxxxxx <mailto:keith.esau@xxxxxxx> >
>>> wrote:
>>>> When I compile my program on Windows in debug mode (shared lib), it runs
>>>> fine. But when I make the release version (with staticlib), a DOS window
>>>> appears and flashes the message "Program too big to fit in memory" and then
>>>> immediately quits.
>>>>
>>>> How do I fix this? (I could find nothing in the FAQ or KnowledgeBase.
>>>>
>>>> Qt version 4.1.4 commercial
>>>> Windows 2000 Service Pack 4 (via Terminal Services)
>>>> 3GB RAM
>>>> Using Visual Studio 2003 .NET, latest patches
>>>>
>>>> Does the same thing if I copy my program to a Windows XP Pro machine.
>>>>
>>>> Keith Esau
>>>
>>>
>>> Keith,
>>>
>>> That rings a bell. Are you loading something really big on the stack? For
>>> example, did you statically allocate a big array globally, or in your
>>> main()?
>>>
>>>
>>> Regards,
>>> Glen.
--
[ signature omitted ]
Message 6 in thread
Hi Keith,
Do you get the same thing when running on a Mac?
-Rob
Keith Esau wrote:
>We do not want the release version to require Qt DLLs. If it doesn't work as
>static for the release version, Qt is useless. The only reason the debug
>version uses DLLs is for speed in the development process.
>
>BTW, the application size is over 10MB. (Only 8.4MB on the debug version
>that uses DLLs.)
>
>So, I am still stuck at the same place. I am a Mac/Unix geek, so I really on
>Qt to get the Windows settings correct. It appears some Windows 'header'
>info is incorrect, but what do I do in Qt to fix it?
>
>Keith
>
>On 08-01-2006 5:56 PM, "Glen van de Mosselaer" wrote:
>
>
--
[ signature omitted ]
Message 7 in thread
I just got the Mac version running yesterday, and it is only for debug
purposes. No problem on Mac, this is a Windows specific issue.
We are porting a large non-Qt cross-platform application to Qt, Until
yesterday, we were primarily working on the Windows version. Mac is not a
targeted platform, but helps for getting the other Unix platforms working
(quicker development and debugging abilities).
On 08-02-2006 12:41 PM, "Robert E. Hartley" wrote:
> Hi Keith,
>
> Do you get the same thing when running on a Mac?
>
> -Rob
>
> Keith Esau wrote:
>
>> We do not want the release version to require Qt DLLs. If it doesn't work as
>> static for the release version, Qt is useless. The only reason the debug
>> version uses DLLs is for speed in the development process.
>>
>> BTW, the application size is over 10MB. (Only 8.4MB on the debug version
>> that uses DLLs.)
>>
>> So, I am still stuck at the same place. I am a Mac/Unix geek, so I really on
>> Qt to get the Windows settings correct. It appears some Windows 'header'
>> info is incorrect, but what do I do in Qt to fix it?
>>
>> Keith
--
[ signature omitted ]
Message 8 in thread
Keith,
I was suggesting that you switch to the DLLs as a diagnostic step to see if
the static lib is really the problem.
Glen.
On 8/2/06, Keith Esau <keith.esau@xxxxxxx> wrote:
>
> We do not want the release version to require Qt DLLs. If it doesn't work
> as
> static for the release version, Qt is useless. The only reason the debug
> version uses DLLs is for speed in the development process.
>
> BTW, the application size is over 10MB. (Only 8.4MB on the debug version
> that uses DLLs.)
>
> So, I am still stuck at the same place. I am a Mac/Unix geek, so I really
> on
> Qt to get the Windows settings correct. It appears some Windows 'header'
> info is incorrect, but what do I do in Qt to fix it?
>
> Keith
>
> On 08-01-2006 5:56 PM, "Glen van de Mosselaer" wrote:
>
> > Keith,
> >
> > Never mind. A quick Google on the error message reveals that this is
> usually a
> > corrupt program header. Or that you're not actually compiling to an
> executable
> > format.
> >
> > http://blogs.msdn.com/oldnewthing/archive/2006/01/30/519388.aspx
> > (this is a great blog, BTW)
> >
> > Bad linker parameters in the Release profile? Bad "General: Project
> Default"?
> > I'd guess it's something in the Project properties. A corrupt static Qt
> > library, possibly? What happens if you build Release with Qt as a DLL?
> >
> >
> > Glen.
> >
> > On 8/1/06, Keith Esau <keith.esau@xxxxxxx> wrote:
> >> There is more global data in the debug version than the release
> version, so
> >> that shouldn't be the problem.
> >>
> >> Keith
> >>
> >>
> >> On 08-01-2006 4:27 PM, "Glen van de Mosselaer" wrote:
> >>
> >>> On 8/1/06, Keith Esau < keith.esau@xxxxxxx <mailto:keith.esau@xxxxxxx>
> >
> >>> wrote:
> >>>> When I compile my program on Windows in debug mode (shared lib), it
> runs
> >>>> fine. But when I make the release version (with staticlib), a DOS
> window
> >>>> appears and flashes the message "Program too big to fit in memory"
> and then
> >>>> immediately quits.
> >>>>
> >>>> How do I fix this? (I could find nothing in the FAQ or KnowledgeBase.
> >>>>
> >>>> Qt version 4.1.4 commercial
> >>>> Windows 2000 Service Pack 4 (via Terminal Services)
> >>>> 3GB RAM
> >>>> Using Visual Studio 2003 .NET, latest patches
> >>>>
> >>>> Does the same thing if I copy my program to a Windows XP Pro machine.
> >>>>
> >>>> Keith Esau
> >>>
> >>>
> >>> Keith,
> >>>
> >>> That rings a bell. Are you loading something really big on the stack?
> For
> >>> example, did you statically allocate a big array globally, or in your
> >>> main()?
> >>>
> >>>
> >>> Regards,
> >>> Glen.
>
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
> "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
>
>
Message 9 in thread
Considering that that takes about 10 hours (to rebuild Qt and my application
twice), I¹ll explore other options first.
On 08-02-2006 2:51 PM, "Glen van de Mosselaer" wrote:
> Keith,
>
> I was suggesting that you switch to the DLLs as a diagnostic step to see if
> the static lib is really the problem.
>
>
> Glen.
Message 10 in thread
> Considering that that takes about 10 hours
Sounds like a one of those overnite-jobs to me ;-)
Regards,
Malte
--
[ signature omitted ]
Message 11 in thread
"Keith Esau" <keith.esau@xxxxxxx> wrote in message
news:C0F673E1.58FC%keith.esau@xxxxxxxxxx
> Considering that that takes about 10 hours (to rebuild Qt and my
> application
> twice), I¹ll explore other options first.
Try to build a release version of any Qt example, linking against the
static Qt library. If you have configured Qt as static using
"configure -static", and rebuilt the whole Qt tree, then the examples
should all have been built already.
If that fails, then I'd suspect a corrupted Qt library. Try to rebuild it.
Volker
--
[ signature omitted ]
Message 12 in thread
Well, I found a temporary solution. I have to link the application under
Visual Studio 2003 instead of on the command line. The resulting application
is now 5.4MB (instead of over 10MB).
I suspect that 'link' is failing on the command line for some reason
(probably a memory limitation) that does not happen when run under the
Visual Studio application.
On 08-02-2006 12:35 PM, "Keith Esau" wrote:
> We do not want the release version to require Qt DLLs. If it doesn't work as
> static for the release version, Qt is useless. The only reason the debug
> version uses DLLs is for speed in the development process.
>
> BTW, the application size is over 10MB. (Only 8.4MB on the debug version
> that uses DLLs.)
>
> So, I am still stuck at the same place. I am a Mac/Unix geek, so I really on
> Qt to get the Windows settings correct. It appears some Windows 'header'
> info is incorrect, but what do I do in Qt to fix it?
>
> Keith
>
>> On 8/1/06, Keith Esau < keith.esau@xxxxxxx <mailto:keith.esau@xxxxxxx> >
>> wrote:
>> When I compile my program on Windows in debug mode (shared lib), it runs
>> fine. But when I make the release version (with staticlib), a DOS window
>> appears and flashes the message "Program too big to fit in memory" and
>> then
>> immediately quits.
>>
>> How do I fix this? (I could find nothing in the FAQ or KnowledgeBase.
>>
>> Qt version 4.1.4 commercial
>> Windows 2000 Service Pack 4 (via Terminal Services)
>> 3GB RAM
>> Using Visual Studio 2003 .NET, latest patches
>>
>> Does the same thing if I copy my program to a Windows XP Pro machine.
>>
>> Keith Esau
--
[ signature omitted ]
Message 13 in thread
On 8/3/06, Keith Esau <keith.esau@xxxxxxx> wrote:
> Well, I found a temporary solution. I have to link the application under
> Visual Studio 2003 instead of on the command line. The resulting application
> is now 5.4MB (instead of over 10MB).
>
> I suspect that 'link' is failing on the command line for some reason
> (probably a memory limitation) that does not happen when run under the
> Visual Studio application.
That sounds silly :). Have you checked that the parameters are the
same? And that the paths and libs are the same as well?
--
[ signature omitted ]
Message 14 in thread
Thanks! That was sort of the problem but helped me find the real problem.
QMake is generating a 'lib' command instead of a 'link' command because I
misunderstood CONFIG += staticlib to 'use' the static libraries (instead of
generate a static library).
Seems obvious, now that I found it...
Keith
On 08-04-2006 1:42 AM, "Robin Ericsson" wrote:
> On 8/3/06, Keith Esau <keith.esau@xxxxxxx> wrote:
>> Well, I found a temporary solution. I have to link the application under
>> Visual Studio 2003 instead of on the command line. The resulting application
>> is now 5.4MB (instead of over 10MB).
>>
>> I suspect that 'link' is failing on the command line for some reason
>> (probably a memory limitation) that does not happen when run under the
>> Visual Studio application.
>
> That sounds silly :). Have you checked that the parameters are the
> same? And that the paths and libs are the same as well?
--
[ signature omitted ]
Message 15 in thread
hallo all,
i have something problem, when tried create class
public QObject like this :
#include <QObject>
class tes : public QObject{
public:
tes();
~stes(){}
public slots:
void tes1(){ cout<<"succes"<<endl;}
signals:
void tesSignal(int a);
};
tes::tes(){
connect(this, SIGNAL( tesSignal(int a)),
this, SLOT( tes1()));
}
after compile and run has been message
"Object::connect: No such signal
Stuff::valueChanged(int a)"
and slot tes1() is not called;
any body help me about its.
please...
thanks before
Djuanda
Send instant messages to your online friends http://uk.messenger.yahoo.com
--
[ signature omitted ]
Pages: Prev | 1 | 2 | Next
