From: "Egil H. H�vik" <egil.harald.hoevikNOSPAM@REMOVEkongsberg.com>
Subject: Re: Interrupt handler seems not to be called in GNAT 3.15p
Date: Thu, 16 Jun 2005 10:03:57 +0200
Date: 2005-06-16T10:03:57+02:00 [thread overview]
Message-ID: <d8rbfi$o7m$1@kda-news.kongsberg.com> (raw)
In-Reply-To: 1118849941.554713.60100@g14g2000cwa.googlegroups.com
> When running the program SIGSEGV is raised twice (which I can see only
> in gdb) for the same memory location and the program terminates. If I
> put a delay 5.0 (or some other time) statement just before accessing
> the memory, I also get the output of the exception handler, which
> means an exception (PROGRAM_ERROR) is raised.
>
> Can anyone give me a hint? Is this a known problem with GNAT 3.15p?
> Is it possible to handle SIGSEGV at all in this environment?
Have you looked at pragma Attach_Handler?
pragma Unreserve_All_Interrupts;
protected Handler is
procedure Handle_SIGSEGV;
pragma Attach_Handler( Handle_SIGSEGV, Ada.Interrupts.Names.SIGSEGV );
end Handler;
~egilhh
next prev parent reply other threads:[~2005-06-16 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 15:39 Interrupt handler seems not to be called in GNAT 3.15p Thorsten
2005-06-16 6:52 ` David C. Hoos, Sr.
2005-06-16 7:38 ` Thorsten
2005-06-16 8:03 ` Egil H. H�vik [this message]
2005-06-16 9:36 ` Thorsten
2005-06-17 8:33 ` Thorsten
2005-06-17 8:47 ` Duncan Sands
2005-06-22 10:04 ` Thorsten
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox