Re: Operator new failing in windows after several days of operation
- From: "Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@xxxxxxxxxxxxxxx>
- Date: Wed, 10 Aug 2005 22:45:43 -0700
Adrian Vacaliuc wrote:
>> Questions:
>> 1. Are you linking with thrownew.obj? If not, you have a
>> non-conforming implementation of ::operator new(). See
>> http://msdn.microsoft.com/msdnmag/issues/03/09/LegacySTLFix/default.aspx
>> for a thorough discussion.
>
> No. I am doing nothing more than linking to the multithreadded DLL
> runtime. I will investigate your link furthur.
I think this is near the heart of your problem. Link with thrownew.obj so
new won't return null. If you disassemble thrownew.obj, you should be able
to identify the place where the out of memory exception is thrown. Set a
breakpoint there while running under windbg and wait.
>> 4. Is the program a monolithic EXE, or is it broken into one or more
>> DLLs? If so, what are the compiler and linker settings for the DLLs?
>
> Many dlls. I can post them all, if you think it would help, but it
> would be quite verbose. Would you like me to do so?
I don't think posting more would help - everything that you've posted here
looks fine to me, with the exception of thrownew.obj.
-cd
.
- References:
- Operator new failing in windows after several days of operation
- From: Adrian Vacaliuc
- Re: Operator new failing in windows after several days of operation
- From: Carl Daniel [VC++ MVP]
- Re: Operator new failing in windows after several days of operation
- From: Adrian Vacaliuc
- Operator new failing in windows after several days of operation
- Prev by Date: Re: Operator new failing in windows after several days of operation
- Next by Date: Linker error and no classes appear
- Previous by thread: Re: Operator new failing in windows after several days of operation
- Next by thread: "delete" causes prog to crash!
- Index(es):
Relevant Pages
|