Mail Archives: djgpp/2002/02/09/20:00:18
boohiss wrote:
> Anyway, it doesn't seem that Allegro questions are frowned upon in
> here, so I'd thought I'd ask away.
I'm new to this newsgroup so I don't know what policies it has, but you
will probably be more on-topic on Allegro's mailing lists (see
http://alleg.sourceforge.net/maillist.html ).
> I tried writing out a basic load bitmap and blit to screen program
> like I've done lots of times before successfully, but this time, the
> program compiles fine with no errors or warnings, but upon running the
> program, it reboots my computer!
This sounds like you are corrupting memory in some way. To debug in this
nasty kind of situation, you can try to scatter calls to
al_trace("%d",__LINE__) all over your code. This will print the line
number in the source code to the file allegro.log, so the end of that
file will contain the lines that were executed just before your computer
reboots. Another technique is to cut away big pieces of code. If it
still reboots, then at least you know that it was independent of that
part of the program. If you still can't figure out what's going wrong,
you can post a short (< 20 lines) program on Allegro's mailing list that
reproduces the error.
> I also have noticed that RHIDE seems to be acting strangely. If I
> type "rhide file.cc" it won't bring up file.cc, but insteads brings up
> another source file that I worked on some weeks ago (the same file
> everytime)
This usually happens if you have saved a rhide project file in the same
directory: it will open the project, overriding files passing on the
command line.
> Both these things seemed to occur around the same time, so I figure
> they must be related.
I don't think so.
Good luck!
--
Sven Sandberg svsa1977 AT student DOT uu DOT se home.student.uu.se/svsa1977
- Raw text -