From: alrc AT task DOT com DOT br (Andre Chrcanovic) Newsgroups: comp.os.msdos.djgpp Subject: Re: gprof with all zero execution times in version 2.03 Date: 14 May 2003 11:07:38 -0700 Organization: http://groups.google.com/ Lines: 19 Message-ID: <5c9be5c2.0305141007.3e81e5d2@posting.google.com> References: <200305121929 DOT h4CJTEN08938 AT delorie DOT com> <5c9be5c2 DOT 0305130628 DOT 45188bfd AT posting DOT google DOT com> <5c9be5c2 DOT 0305131309 DOT 7d688c74 AT posting DOT google DOT com> NNTP-Posting-Host: 200.165.11.92 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1052935659 30473 127.0.0.1 (14 May 2003 18:07:39 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: 14 May 2003 18:07:39 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hans-Bernhard Broeker wrote in message news:... > > There, you did it. Unless you did that *very* carefully, this almost > certainly is what broke the profile data collection. Gprof relies on > standard timer ticks to do its work. OK. Maybe I was not very careful... I wrote the handler based on the information I found in the FAQ (item '18.9 How to hook hardware interrupts'). Is there a way to change the timer and still have the profile to work? Charles Sandmann mentions that "If you need your own timer routine then you need to chain to the original timer if you want profiling by time to work". I tried to use '_go32_dpmi_chain_protected_mode_interrupt_vector', as described in the 'Guide: Interrupts Overview' document, but this crashes the program... Is the version of the document I found in DJGPP's site not updated? I also tried the example code listed there and it also crashes...