From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: something wierd is going on... Date: 24 Feb 2000 11:33:30 GMT Organization: Aachen University of Technology (RWTH) Lines: 44 Message-ID: <8934ua$bfk$1@nets3.rz.RWTH-Aachen.DE> References: <38B3192A DOT F17E3572 AT geocities DOT com> <8909up$mbp$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <38B4508A DOT 754E1FFB AT geocities DOT com> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 951392010 11764 137.226.32.75 (24 Feb 2000 11:33:30 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 24 Feb 2000 11:33:30 GMT User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586)) Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Sahab Yazdani wrote: > the second problem is that since DrawString is a part of a class, > showing you the source code would prove to be quite difficult (as people > in the group might get mad). is filled with valid values using > sprintf. You don't need to show us the whole source of the class. But we definitely need at least *some*thing to look at, in order to be able to help you. We're not psychic, see? Even the declaration of the DrawString method might already be helpful. You're depriving yourself of the more powerful help we might have to offer, if you don't show us a minimal example case. Throw out everything in your program, until you find a source code where every part of it seems to be necessary to recreate the problem. If that source still seems too long for posting it to the mailing list and newsgroup, you can still mail it to me or maybe Eli, directly. > My own system is Windows 98 (not SE) and I've tried it on Pure DOS > (CSWDMPI), Windows 95, Windows 95 OSR 2, a couple other Windows 98 and a > Windows 98 SE. and only my own system works fine... This is getting curiouser and curiouser. From the above, the only possible conclusion would be that it's some configuration difference between your machine and those other ones. Things to watch out for would mainly be the DOS box settings. Also check out if you have a Win32 debugger hooked into the General Protection Fault handling dialog. Is DrWatson running on your machine? > If it would help, the crash is a page fault and its a write error. I think that easily supports my initial suspicion that you've been writing into a string constant. If you want to be extra sure, try compiling with the -fwritable-strings, once, and see if the executable you get from that still crashes, on those other machines. > I have tried symifying, but its really hard to tell what works and > what doesn't when you can't check it on your own computer. Even if you can't make anything out of it, please *do* send in the symified dump. Chances are one of the experts around here will be able to spot things you didn't. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.