*BSD News Article 71880


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!howland.reston.ans.net!surfnet.nl!tuegate.tue.nl!news.IAEhv.nl!news
From: cees@iaehv.nl (Hans Zuidam)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Alarms & gdb
Date: 24 Jun 1996 07:05:43 GMT
Organization: Brand Innovators
Lines: 20
Message-ID: <4qleo7$m7q@news.IAEhv.nl>
References: <4q8msm$j0o@news.IAEhv.nl> <31CC2D7B.77B0@www.play-hookey.com>
NNTP-Posting-Host: pm2d01.iaehv.nl
Mime-Version: 1.0
X-Newsreader: WinVN 0.99.2

In article <31CC2D7B.77B0@www.play-hookey.com>, kbigelow@www.play-hookey.com says...
>Hans Zuidam wrote:
>> I have a problem debugging a program which uses the interval timer to
>> periodically do some work. Each time I try to continue after a
>> breakpoint, the alarm has gone off and I get dumped back into gdb.
  
> ... Could the crom daemon control the timing, with perhaps a control
> file to tell the regular task's script whether or not to take action?

Thanks for your suggestion, but it will not work in my case: the switch
happens every so many milliseconds. It would overload cron somewhat. The
application is actually a real-time kernel running on top of FreeBSD and
the interval timer is used to simulate a clock interrupt. So each time
an alarm goes off, a dispatcher is called to see what to do next (switch
tasks, do some I/O and so on.)

Suggestions how to solve the debug problem are still welcome,

					Hans