From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg) Newsgroups: comp.os.msdos.djgpp Subject: Re: gprof with all zero execution times in version 2.03 Date: 14 May 2003 07:20:30 GMT Organization: Ericsson Erisoft AB, Sweden Lines: 25 Message-ID: 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: lws256.lu.erisoft.se X-Newsreader: TIN [version 1.2 PL2] To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Andre Chrcanovic (alrc AT task DOT com DOT br) wrote: : I compiled all libraries using the -g and -pg flags, but the : executable generated does not run: it crashes. When I remove -g and : -pg from the libraries that have some assembly code (I use nasm), the : executable runs, but the results were the same. What is the influence : of nasm generated objects in profiling an executable? No idea. I don't see why that would matter except some time will be logged on wrong functions. But then I don't do much profiling so I don't know what I'm talking about. Does nams have a -pg flag or something? Then perhaps that is broken or incompatible? : Regarding the timers, I change the PC timer and have my own timer : interrupt routine. I need a 5 ms interrupt to scan telephony : hardware... Oh, so it took 0.28 seconds for you to install that... (See Charles reply.) Right, MartinS