From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6c88d608f416c108 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-11-18 19:06:40 PST Newsgroups: comp.lang.ada Path: nntp.gmd.de!xlink.net!howland.reston.ans.net!cs.utexas.edu!usc!crash!telesoft!pmartin From: pmartin@alsys.com (Pascal Martin @lone) Subject: Re: Anyone built a debugger for Ada? Message-ID: Sender: news@alsys.com (USENET News Admin @flash) Organization: Alsys Group, San Diego, CA, USA References: <3a6mbe$clc@coyote.rain.org> Date: Fri, 18 Nov 1994 21:53:43 GMT Date: 1994-11-18T21:53:43+00:00 List-Id: In gijs@mbase97.xs4all.nl (Maarten Landzaat) writes: >In <3a6mbe$clc@coyote.rain.org>, Henri Altarac writes: >>Maarten Landzaat (gijs@mbase97.xs4all.nl) wrote: >>: Hi, >> >>: I'm trying to build a simple debugger for Ada programs, because Adaprobe >>: (debugger from Alsys) does not work in our environment. I'll describe >> >> >>Can you elaborate. Why cannot you use AdaProbe? (and what did Alsys say ?) >Our target is a special 68000 board. I don't know the details, since >another team actually deals with this thing, but I understand that >the compiler or parts of it has been rewritten for this particular target. >Also, there is an Ada_Connect package that allows us to talk to the >68000 over the bus. The team told me that when this package is used, >Adaprobe doesn't run. >Alsys says: "We'll fix it". It's been saying this for over a year now. >It's still not fixed, so in the meantime we're doing what we can. I remember a problem that was a deadlock on the target side when both the application and AdaConnect was trying to access the same Enet-1 Ethernet board. the problem was due to the way the Enet-1 board is managing the interrupt. Actually, this was the Enet-1 board that was blocked.. because it was unable to do anything else while waiting for an interrupt acknowledge. But the program was running in the debugger part, with all the Interrupts blocked. Do you called the Enet-1 vendor (if you use this board), so to have a meeting together with you (the customer), Alsys and the Enet-1 vendor ? I think this is the more effective way to solve such problems. But there is a possible confusion here, as you talk about a 'bus': (ads section starts here :-) Alsys has a multiprocessor communication package, compatible with the previous AdaConnect for Enet-1, named AdaConnect/BUS. (ads section ends here :-) Perhaps you was talking about this one. So here is a small discussion: This package has been debugged with AdaProbe. We don't have encountered any problem with Adaprobe (the Alsys debugger), except one, that is a general one: in AdaConnect BUS, there are timeout. When you stop one processor, because a breakpoint, all the other processors discover your own one do not answer anymore. So the break all the established connections. And your system cannot work anymore. There is, in the AdaConnect documentation, a description of how to remove this timeout feature. I hope this may help. Pascal.