This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Possible gcc bug with setjmp()?

From: Jeroen Demeyer <jdemeyer at cage dot ugent dot be>
To: gcc-help at gcc dot gnu dot org
Date: Tue, 16 Apr 2013 18:16:20 +0200
Subject: Re: Possible gcc bug with setjmp()?
References: <516D3BA2 dot 7050208 at cage dot ugent dot be> <516D584D dot 6010503 at redhat dot com>

On 04/16/2013 03:55 PM, Florian Weimer wrote:

On 04/16/2013 01:53 PM, Jeroen Demeyer wrote:

     int x = setjmp(env);
     int n = g(x);
     fprintf(stderr, "x = %i, n = %i\n", x, n);

     if (n == 0) exit(0);
     if (x) abort();
     longjmp(env, 42);


I think you should file this as a bug report.  I don't think the GCC
behavior is covered by the longjmp() exceptions for automatic variables.


Thanks! Reported as http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56982

References:
- Possible gcc bug with setjmp()?
  - From: Jeroen Demeyer
- Re: Possible gcc bug with setjmp()?
  - From: Florian Weimer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]