public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Dan Ingold" <dan@objective-design.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8966: Lost exceptions across library boundaries
Date: Mon, 16 Dec 2002 16:46:00 -0000	[thread overview]
Message-ID: <20021217004602.20653.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8966; it has been noted by GNATS.

From: "Dan Ingold" <dan@objective-design.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, 
  gnu@ingold.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/8966: Lost exceptions across library boundaries
Date: Mon, 16 Dec 2002 16:42:40 -0800

 Wolfgang,
 
 In retesting, I found that my simplified example does not 
 exhibit the error.  My full application does, but it's too 
 complex to submit for a bug report.  Will you please 
 delete my bug report for now, and I'll resubmit when I 
 have a better example?  Thank you, Wolfgang.
 
 Regards,
 Dan
 
 On 17 Dec 2002 00:28:15 -0000
   bangerth@dealii.org wrote:
 >Synopsis: Lost exceptions across library boundaries
 >
 >State-Changed-From-To: open->feedback
 >State-Changed-By: bangerth
 >State-Changed-When: Mon Dec 16 16:28:13 2002
 >State-Changed-Why:
 >     Unfortunately, the attachment got lost. Can you 
 >resend it
 >     so that I can append it to the bug report?
 >     
 >     Thanks
 >       Wolfgang
 >
 >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8966
 


             reply	other threads:[~2002-12-17  0:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 16:46 Dan Ingold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-16 16:52 bangerth
2002-12-16 16:28 bangerth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021217004602.20653.qmail@sources.redhat.com \
    --to=dan@objective-design.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).