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.1 required=5.0 tests=BAYES_00,FREEMAIL_FROM, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,c96afc4bd5bda0f0 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!news1.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local1.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail NNTP-Posting-Date: Mon, 17 Jan 2005 18:33:44 -0600 From: "Jeff C" Newsgroups: comp.lang.ada References: Subject: Re: Gnat 3.4.2 tasking errorcodes windows Date: Mon, 17 Jan 2005 19:33:50 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-RFC2646: Format=Flowed; Original Message-ID: <99KdnVVDtLT1xHHcRVn-iQ@comcast.com> NNTP-Posting-Host: 24.147.74.171 X-Trace: sv3-131EEMkqHxTBo687AI/M068U+ZbueR1zipsfSTcs8WuwCp+NLMFqmwmg7WY5UyqMsXQdKpo9Z9wlR2i!uI4NjVtQ4uXRWZEak3lteF6Dq3Sr0puY6d+9XxlaRIppbxaRlbd2vt7YGXgvug== X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.22 Xref: g2news1.google.com comp.lang.ada:7884 Date: 2005-01-17T19:33:50-05:00 List-Id: "Bj�rn Lundin" wrote in message news:mailman.65.1105991123.527.comp.lang.ada@ada-france.org... Hello all! A couple of weeks I sent the mail below, but got no answers. Well, I then tried to use gnat 3.4.2 from minGW, instead of 3.15.p, but I got he same results still. Besides, it it only me that misses libaddr2line, used to print stacktraces? It was included in 3.15p, but now I cant find it :( Looks to me like this function returns a thread specific value so it should be ok. Clearly it is not ok for some reason. I'd guess something about the exception propagation within the threaded run-time support is clearing that error value. I see no reason why it should I recommend you submit a bugzilla bug at the gcc site. At the very least this should be documented.