Re: excessive stack space usage in NTDLL

2005-10-03 Thread Eric Pouech
I guess the app itself uses so much stuff. There is a lot more backtrace below, but just hexcode. that's (likely) because you don't have debug info for the app I stopped scrolling after 2 entries. Can I do winedbg do follow CreateProcess()es? this hasn't been fully tested, I don't reco

Re: excessive stack space usage in NTDLL

2005-10-03 Thread Marcus Meissner
On Mon, Oct 03, 2005 at 02:36:55PM +0200, Alexandre Julliard wrote: > Marcus Meissner <[EMAIL PROTECTED]> writes: > > > No recursion as far as I can see. I get this backtrace: > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 1469332400 (LWP 24408)] > > 0x5577e5

Re: excessive stack space usage in NTDLL

2005-10-03 Thread Alexandre Julliard
Marcus Meissner <[EMAIL PROTECTED]> writes: > The stackspace usage in dlls/ntdll/directory.c is affecting > programs. One installer crashes because of it I suspect. Is it by any chance because it does a recursive search of the disk and runs out of stack? If that's the case you'll most likely see

excessive stack space usage in NTDLL

2005-10-03 Thread Marcus Meissner
Hi, The stackspace usage in dlls/ntdll/directory.c is affecting programs. One installer crashes because of it I suspect. objdump -d directory.o|grep "sub.*[0-9a-f][0-9a-f][0-9a-f],%esp" wine_nt_to_unix_file_name - 0x5f0 (1520 byte) (in this my sample program crashes