gcc3.2.3 : exception caught, but still segment fault

gcc3.2.3 : exception caught, but still segment fault

[lin q]

OK, I have some update on this.

I find that I must use "catch (...)" to catch the exception, otherwise there 
always is a segment fault.

I tried throw an integer and catch an integer, throw a string and catch a 
string and that throw a self-defined class object and catch that class, 
these all do not work.

I tried tracing the flow in gdb, but it can only go to the catch statement 
and then I see something about SIGNAL and flow lost.

But once I use "catch (..)" then whatever type is thrown, it is fine.

It is strange. Any body see it?


Hi,
  I am using gcc3.2.3 as the compiler for my c++ code on Red Hat Linux 
Enterprise 3. I find that even an exception is caught, "Segment Fault" is 
still thrown out and program crashes.

  Here is my code,
int func0(){
   ...
   if (...some condition...){
     throw MyException();
   }
}

char* func(){
   try{
      ...
      func0();
   }
   catch (MyException& ){
      cout << "Hey catch exception" << endl;
      return NULL;
   }
}

  In running the code, I can see that "Hey catch exception", and then 
"Segment Fault", it never returns to the caller of func().

  Is this a known problem?

Thanks.
  I wonder

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

Re: gcc3.2.3 : exception caught, but still segment fault

[Fred Labrosse]

On Wed, 18 May 2005 20:27:52 -0600
"lin q" <linq936@hotmail.com> wrote:

> OK, I have some update on this.
> 
> I find that I must use "catch (...)" to catch the exception, otherwise
> there  always is a segment fault.

What do you mean by "catch (...)"?  You do have one in the code you
sent.

Fred

Re: gcc3.2.3 : exception caught, but still segment fault

[Eljay Love-Jensen]

Hi lin q,

Use gdb to step through the problem area.  Set break points inside your catch handler.

I suspect that the caller of func() is dereferecing the NULL pointer, causing a segment fault.

HTH,
--Eljay

gcc3.2.3 : exception caught, but still segment fault

[lin q]

Hi,
  I am using gcc3.2.3 as the compiler for my c++ code on Red Hat Linux 
Enterprise 3. I find that even an exception is caught, "Segment Fault" is 
still thrown out and program crashes.

  Here is my code,
int func0(){
   ...
   if (...some condition...){
     throw MyException();
   }
}

char* func(){
   try{
      ...
      func0();
   }
   catch (MyException& ){
      cout << "Hey catch exception" << endl;
      return NULL;
   }
}

  In running the code, I can see that "Hey catch exception", and then 
"Segment Fault", it never returns to the caller of func().

  Is this a known problem?

Thanks.
  I wonder

_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee® 
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963