From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: docs for symify Date: Thu, 20 Jan 2000 23:34:48 +0200 Organization: NetVision Israel Lines: 19 Message-ID: <38877F78.B88C616@is.elta.co.il> References: <38847477 DOT 22483872 AT NotesXnt> <2vae8s87k324q2d8hs8eteg8mtqccu2snd AT 4ax DOT com> NNTP-Posting-Host: ras2-p114.rvt.netvision.net.il Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.netvision.net.il 948404085 13382 62.0.172.238 (20 Jan 2000 21:34:45 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 20 Jan 2000 21:34:45 GMT X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,ru,hebrew To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com gunno wrote: > > My silly question It wasn't a silly question. > was about if the stack dumps in these crash message boxes > could be used to something useful, similar to what symify can do. Not really, because when such a message pops, it really means that the problem was inside Windows (usually inside VMM, the Virtual Machine Manager). So the info presented there points into Windows' own guts, not into the DJGPP program. It is impossible to interpret that info without sources of Windows, and even if you had the sources, it would be very hard to make the connection between the problem inside VMM and the original bug in the DJGPP program. And sometimes the message that pops doesn't even tell anything close to a stack dump.