[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
more patches more newlib-1.16.0 : setjmp & longjmp for 4.9 branch
- Date: Mon, 02 Mar 2009 16:30:58 -0500
- From: feng1 at bnl.gov (Kate Feng)
- Subject: more patches more newlib-1.16.0 : setjmp & longjmp for 4.9 branch
Ralf Corsepius wrote:
> Kate Feng wrote:
>> Attached is the patches for newlib-1.16.0. The setjmp() and longjmp()
>> are broken, which could affect their function in the 4.9. branch.
>> The patch for the setjmp.S is only for powerPC port, which was tested
>> for my applications. The path for the setjmp.h should be applied to
>> all platforms.
> Some questions:
> * Which bug is this patch supposed to fix?
> Please elaborate.
> * Whatever you are trying to fix, is almost certainly not RTEMS
> specific but architecture specific
> => Your use of __rtems__ is not the "right way" to do it.
The machine/powerpc/setjmp.S file is probably only linked to powerPC port.
Thus, it's probably OK. However, setjmp() , when called, will trigger
message of :
Uhuuuh, Exception 10 in unknown task???".
Using sigsetjmp(buf, 1) did not solve the problem. Thus,
I simply apply the patch from the newlib1.15.0, which I used for the
RTEMS4.8.0. Perhaps, it was implemented wrongly in 4.8 , instead ?
I agree with you that the patch fixes the problem, but ties its function
specific. At this point, I do remember reading about that 'setjmp' and
should be used carefully that there are other more graceful ways to
This is my memory from last century that I guess I would have to dig
the more elegant solution........
Thanks a lot for your pointer. Perhaps, it is better not to apply the
patch so that
it does not add architecture specific patch...... Please advise.