You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug report was migrated from our old Bugzilla tracker.
Reported in version: HG 2.0 Reported for operating system, platform: All, All
Comments on the original bug report:
On 2019-09-14 01:09:48 +0000, Rudolf Polzer wrote:
When using SDL_DYNAMIC_API=SDL_DYNAMIC_API=/usr/lib/x86_64-linux-gnu/libSDL2.so ./someprogram, where libSDL2.so is 2.0.10 and ./someprogram is statically linked against 2.0.9, the program loops endlessly in SDL_Init.
I already went through gdb with this, and found the root cause:
But the loaded library should be 2.0.10, the statically-linked version is 2.0.9, and it should have a tablesize that's less than sizeof (jump_table) at this point.
(Unless I'm misreading this code and missing the bug) we had to be in the wrong entry point here (2.0.10 library calling into static 2.0.9's SDL_DYNAPI_entry.
I'll try to reproduce here.
--ryan.
On 2019-09-14 22:24:48 +0000, Rudolf Polzer wrote:
Sorry, I made a mistake in the OP.
In my concrete scenario, the statically linked version was 2.0.10 and the .so was 2.0.9.
This is not supposed to work, but it should not loop endlessly either. Desired result is either an error or a warning being printed, and the program either continuing or exiting, but not looping endlessly.
On 2019-09-15 02:55:57 +0000, Ryan C. Gordon wrote:
(In reply to Rudolf Polzer from comment # 3)
This is not supposed to work, but it should not loop endlessly either.
Oh, I see. Yes, that sounds like a bug.
--ryan.
On 2019-09-20 20:47:38 +0000, Ryan C. Gordon wrote:
We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc).
As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change!
Thanks,
--ryan.
On 2019-09-20 20:48:41 +0000, Ryan C. Gordon wrote:
We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc).
As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change!
Thanks,
--ryan.
On 2019-10-14 16:42:04 +0000, Ryan C. Gordon wrote:
This bug report was migrated from our old Bugzilla tracker.
Reported in version: HG 2.0
Reported for operating system, platform: All, All
Comments on the original bug report:
On 2019-09-14 01:09:48 +0000, Rudolf Polzer wrote:
On 2019-09-14 01:11:34 +0000, Rudolf Polzer wrote:
On 2019-09-14 18:14:42 +0000, Ryan C. Gordon wrote:
On 2019-09-14 22:24:48 +0000, Rudolf Polzer wrote:
On 2019-09-15 02:55:57 +0000, Ryan C. Gordon wrote:
On 2019-09-20 20:47:38 +0000, Ryan C. Gordon wrote:
On 2019-09-20 20:48:41 +0000, Ryan C. Gordon wrote:
On 2019-10-14 16:42:04 +0000, Ryan C. Gordon wrote:
The text was updated successfully, but these errors were encountered: