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=-1.3 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,477d2c7239b77805 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-03-08 14:55:13 PST Path: archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!news.tele.dk!small.news.tele.dk!213.56.195.71!fr.usenet-edu.net!usenet-edu.net!enst!enst.fr!not-for-mail From: sk Newsgroups: comp.lang.ada Subject: Re: no crash dump ? Date: Fri, 08 Mar 2002 16:49:26 -0600 Organization: ENST, France Sender: comp.lang.ada-admin@ada.eu.org Message-ID: References: <20020307215639.37cf3f6d.bjorn.lundin@swipnet.se> <20020308172207.2a82c68a.bjorn.lundin@swipnet.se> Reply-To: comp.lang.ada@ada.eu.org NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: avanie.enst.fr 1015628110 75014 137.194.161.2 (8 Mar 2002 22:55:10 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Fri, 8 Mar 2002 22:55:10 +0000 (UTC) Return-Path: X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19-4.3mdk i686) X-Accept-Language: en Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: comp.lang.ada mail<->news gateway List-Unsubscribe: , Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org Xref: archiver1.google.com comp.lang.ada:20961 Date: 2002-03-08T16:49:26-06:00 Hi, If this is the complete code sample for your "Joystick" program, there are no calls within it which actually do an operation likely to cause a system level "core dump". As "anders@localhost.localdomain (Anders Gidenstam)" pointed out, the line Joystick_address : system.address := system'to_address(16#0201#); probably locates the code in your own address space and *not* into the kernel address space. If this is an Intel based platform, the I/O address space is different from the memory address space, so 16#0201# will at best refer to a memory location and not the I/O port 16#0201# If you are running your Linux installation "unhacked" and you are not by-passing the system to talk to your hardware, you might find it easier to use the device drivers and develop your application to "talk" to them (assuming that your Linux installation process recognised your joystick and installed a suitable driver). I would suggest that you do an internet search for "linux device drivers" and you should get several articles explaining how to code and use device drivers. >From there, I would suggest you visit "www.gnuada.org" which has, or has links to, several binding packages for Linux which might make "talking" to device drivers easier ... you never know, someone might have already built a "Joystick" package :-) -- ------------------------------------- -- Merge vertically for real address ------------------------------------- s n p @ t . o k i e k c c m -------------------------------------