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,3cf26033e2e108c9 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-07-03 06:14:03 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.icl.net!newsfeed.fjserv.net!oleane.net!oleane!freenix!enst!enst.fr!not-for-mail From: "David C. Hoos" Newsgroups: comp.lang.ada Subject: Re: "Program received signal SIGSEGV, Segmentation fault". Date: Wed, 3 Jul 2002 08:13:42 -0500 Organization: ENST, France Sender: comp.lang.ada-admin@ada.eu.org Message-ID: References: Reply-To: comp.lang.ada@ada.eu.org NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: avanie.enst.fr 1025702043 43277 137.194.161.2 (3 Jul 2002 13:14:03 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Wed, 3 Jul 2002 13:14:03 +0000 (UTC) Return-Path: X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.0.11 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 X-Original-Cc: sebastian.madunic@avionics.saab.se Xref: archiver1.google.com comp.lang.ada:26841 Date: 2002-07-03T08:13:42-05:00 SIGSEGV is a UNIX signal sent to the process by the operating system when the process attempts to access memory at an illegal address. There are many causes of illegal address, so it is impossible to answer your question more fully without additional information. In the context of an Ada program, it might well be attempting to use an access value which was never initialized, or which has become invalid because the memory which it accesses was freed by a call to an instantiation of Ada.Unchecked_Deallocation. I hope this helps. ----- Original Message ----- From: "Darren" Newsgroups: comp.lang.ada To: Sent: Wednesday, July 03, 2002 7:18 AM Subject: "Program received signal SIGSEGV, Segmentation fault". > Hi, > > I got this message from the GVD debugger when I run my program, > "Program received signal SIGSEGV, Segmentation fault" > > What does it mean? What is the problem? > > Kind regards, > > M > > > _______________________________________________ > comp.lang.ada mailing list > comp.lang.ada@ada.eu.org > http://ada.eu.org/mailman/listinfo/comp.lang.ada >