Ticket #39245

setjmp.h wrong parameters to _setjmp3

Open Date: 2019-05-16 03:13 Last Update: 2019-05-17 06:31

Reporter:
Owner:
(None)
Type:
Status:
Closed
Component:
(None)
MileStone:
(None)
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Invalid
File:
None
Vote
Score: 0
No votes
0.0% (0/0)
0.0% (0/0)

Details

According to https://docs.microsoft.com/en-us/cpp/c-runtime-library/setjmp3

The correct api is int _setjmp3(jmp_buf env, int count, ....) where count is the number of parameters that follow.

On 32-bit, as of e33afcd864a4e90a7b170585d802a3f85fbe7dfe, the setjmp.h that got generated, maps setjmp(buf) to _setjmp3(buf, NULL)

I don't know what issue this causes, but as setjmp (_setjmp3()) is returning -1, it might be an issue.

Also on the same page, _setjmp3 should not be used in a c++ context. The header setjmp does not prevent _setjmp3 for c++.

There's a define USE_NO_MINGW_SETJMP_TWO_ARGS, which controls the number of args to setjmp, but I don't know why yet.

Ticket History (3/3 Histories)

2019-05-16 03:13 Updated by: rich_coe
  • New Ticket "setjmp.h wrong parameters to _setjmp3" created
2019-05-16 03:22 Updated by: rich_coe
Comment

Ignore my comment about setjmp() returning -1.

2019-05-17 06:31 Updated by: keith
  • Status Update from Open to Closed
  • Resolution Update from None to Invalid
Comment

Sorry, but I cannot see any correlation between this report, and the content of our <setjmp.h> implementation, as can be seen here. Consequently, I am closing this, as it appears to be invalid in the MinGW.org context; (we do not support tha products of other projects, which illegally abuse our registered trademark).

Attachment File List

No attachments

Edit

Please login to add comment to this ticket » Login