From: azure@vvf.fi
To: Joe Buck <jbuck@synopsys.com>
Cc: egcs@cygnus.com
Subject: Re: Required gas version? (was: Re: Results for haifa-disabled egcs-971105 g++ testsuite on i586-pc-linux-gnulibc1)
Date: Tue, 11 Nov 1997 06:35:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.971111160336.9359A-100000@quasar.vvf.fi> (raw)
In-Reply-To: <199711100041.QAA19055@atrus.synopsys.com>
On Sun, 9 Nov 1997, Joe Buck wrote:
> > I recently installed egcs-971023 with pgcc-patches
>
> Sorry, if you're going to use the pgcc patches, we have no way of
> verifying that it isn't those patches that are breaking exception
> handling.
I know, sorry if gave a wrong impression. I didn't want to bother
anyone with this potentially pgcc-specific EH-problem, so that's why I
tried just to ask about the version of gas, which hopefully was enough
egcs-specific subject, so that I could find out myself whether upgrading
would help or not.
> I believe that it is. However, there's still at least one EH failure
> on Linux even with the new gas, so your test may still represent a bug.
> Or the problem could be the pgcc patches. Please post your test case.
> If it works for others, then the problem may be the pgcc patches.
> Another possibility is that your test case breaks for everyone.
I also tried my test with egcs-971023 (and gas-970915) without pgcc patches
and it also failed. Here's the code, in case someone is interested to
give it a try:
--- clip -----------------------------------------------------------------
#include <iostream.h>
class Base {
int a;
public:
void setValue(int value) {a=value;}
};
class Derived : private Base {
char* ptr;
public:
void setPV(char* p, int v) {ptr=p; setValue(v);}
};
void a_function(void);
int foobar = 3;
int main()
{
try {
a_function();
}
catch (Derived a) {
cout << 1 << endl;
}
catch (Base a) {
cout << 2 << endl;
}
catch (...) {
cout << 3 << endl;
}
return 0;
}
void a_function(void)
{
Base hmm;
Derived hmm2;
int hmm3;
if (foobar == 1) {
throw hmm;
}
else if (foobar == 2) {
throw hmm2;
}
else {
throw hmm3;
}
}
--- clip -----------------------------------------------------------------
It's that "throw hmm3;" above that causes a coredump.
Thanks for your help!
---
Hannu Koivisto | What you see is all you get.
NOYB | - Brian Kernighan
-------------------------------------------------------------
next prev parent reply other threads:[~1997-11-11 6:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-08 7:18 Results for haifa-disabled egcs-971105 g++ testsuite on i586-pc-linux-gnulibc1 Alexandre Oliva
1997-11-08 15:41 ` Joe Buck
1997-11-09 5:00 ` Required gas version? (was: Re: Results for haifa-disabled egcs-971105 g++ testsuite on i586-pc-linux-gnulibc1) azure
1997-11-09 10:58 ` Alexandre Oliva
1997-11-09 16:41 ` Joe Buck
1997-11-10 10:59 ` H.J. Lu
[not found] ` <m0xUyYe-0004ecC.cygnus.egcs@ocean.lucon.org>
1997-11-10 12:13 ` Jason Merrill
1997-11-11 6:35 ` azure [this message]
1997-11-13 10:46 ` H.J. Lu
1997-11-09 10:56 ` Results for haifa-disabled egcs-971105 g++ testsuite on i586-pc-linux-gnulibc1 Alexandre Oliva
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=Pine.LNX.3.96.971111160336.9359A-100000@quasar.vvf.fi \
--to=azure@vvf.fi \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.com \
/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).