On Jun 6 01:15, Dave Korn wrote: > Corinna Vinschen wrote: > > > Not good. I'm puzzled where this allocated 68K region is exactly coming > > from, but it really looks like something which occurs in or near dlopen. > > > > I'm going to debug this further tomorrow. I guess that goes without > > saying, but I'd be glad for any help. > > I'll just suggest that these problems can often be debugged more easily in > windbg than gdb, what with gflags/appverifier heap tracking, !vad, !heap, and > related commands. The gflags FLG_HEAP_ENABLE_TAG_BY_DLL might come in handy > here.
Right. You might have noticed in my mail that I refer to WinDbg already. It has a couple of invaluable helpers. !vprot is one of my favorites, as well as the many available display formats in the memory window. This morning I woke up and suddenly knew what's going on. It's the size of a structure, which had a size of 320 bytes before. Now it has a size of 65596 bytes since the filename stored in it is now a potentially 32K long wide character string. The structure must be shrinked again. I guess I have a patch by tonight. Stay tuned, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
