Xref: news-dnh.mv.net comp.os.msdos.djgpp:4068 Path: news-dnh.mv.net!mv!news.NH.Destek.Net!news2.net99.net!news.cais.net!news.sprintlink.net!malgudi.oar.net!kira.cc.uakron.edu!neoucom.edu!news.ysu.edu!news.ecn.uoknor.edu!paladin.american.edu!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!in1.uu.net!rice!news!sandmann From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: profiling in V2 beta 4 Date: Sat, 30 Dec 1995 10:21:42 CST Organization: Rice University, Houston, Texas Lines: 24 Message-ID: <30e56716.sandmann@clio.rice.edu> References: Reply-To: sandmann AT clio DOT rice DOT edu NNTP-Posting-Host: clio.rice.edu To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp > [2] GDB chokes on any programs GCC'ed with "-pg". It is easy for > me (in hindsight) to think of reasons why this might be (timer interrupt Humm, I didn't test this. Ah yes, I just looked at the source, and this won't work. Programs using alarm() or setitimr() can't be debugged either. There is an easy fix for this in dbgcom.c, but then it disables any program running under the debugger from hooking the timer interrupt (with the change, if it does, it just won't see any tics). You can't get keyboard interrupts in a debugged program, BTW. Other associated bugs: you can't debug a program which uses floating point on a non FPU machine either (that's a longer story), and the debugger gets all hardware (exception) signals and doesn't pass them. OK, I think I came clean on all the bugs I left. dbgcom.c is used by all the debuggers and is supposed to handle all this stuff, but I never had time to write it. I will probably finish the Int 9 keyboard passing stuff first. > Any chance that GDB could recognize that "-pg" was used and sound an alarm? Actually it just ought to be fixed, but I don't have the time to look at it anytime soon, sorry.