Mail Archives: djgpp/1997/02/17/15:01:44
| From: | Alan Marrs <marrs AT signal DOT dra DOT hmg DOT gb>
|
| Newsgroups: | comp.os.msdos.djgpp
|
| Subject: | profiling and ALLEGRO?
|
| Date: | Mon, 17 Feb 1997 09:55:33 +0000
|
| Organization: | Defence Research Agency
|
| Message-ID: | <33082B15.41C6@signal.dra.hmg.gb>
|
| NNTP-Posting-Host: | signal.dra.hmg.gb
|
| Mime-Version: | 1.0
|
| Lines: | 13
|
| To: | djgpp AT delorie DOT com
|
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Are there any important points I should know regarding the use of the
gprof profiler on code using the ALLEGRO library. I've got two separate
programs (both using ALLEGRO). If I compile both with the -pg compiler
flag set one runs fine and I get the profiling info, the other doesn't.
So my question is do I need to be aware of incompatabilities between
ALLEGRO and the use of the -pg compiler flag. BTW how do all of you
ALLEGRO users prefer to debug/profile your code? Do you use gdb/emacs or
RHIDE?
Thanks
Alan Marrs
- Raw text -