We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 641 - repeat a bug of loadKeyboardLayout()
Summary: repeat a bug of loadKeyboardLayout()
Status: RESOLVED WONTFIX
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 1.2.13
Hardware: x86 Windows (All)
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords: target-1.2.14
Depends on:
Blocks:
 
Reported: 2008-11-07 04:01 UTC by cznc
Modified: 2009-10-17 11:05 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description cznc 2008-11-07 04:01:29 UTC 
Hi,

One of my project uses SDL-1.2.13.
It is often sticked at 

DIB_InitOSKeymap (this=0x186f23d0) ./src/video/windib/SDL_dibevents.c:284
287             hLayoutUS = LoadKeyboardLayout("00000409", KLF_NOTELLSHELL);

with 99% cpu occupation, entering from SDL_Init(SDL_INIT_VIDEO).
But when some examples code almose all works well.


It runs at gdb on cygwin(print This GDB was configured as "i686-pc-cygwin"), windows 2000 sp4 , what more on windowsXp which works before reinstalled.
Comment 1 Ryan C. Gordon 2009-09-13 16:33:41 UTC 
Tagging this bug with "target-1.2.14" so we can try to resolve it for SDL 1.2.14.

Please note that we may choose to resolve it as WONTFIX. This tag is largely so we have a comprehensive wishlist of bugs to examine for 1.2.14 (and so we can close bugs that we'll never fix, rather than have them live forever in Bugzilla).

--ryan.
Comment 2 Sam Lantinga 2009-09-21 03:54:47 UTC 
Are you still seeing the issue with SDL from subversion?
http://www.libsdl.org/tmp/SDL-1.2.zip
Comment 3 Sam Lantinga 2009-10-17 11:05:24 UTC 
No response from the customer, I'm closing this for now.  Please reopen this as a 1.3 bug if it's an issue there.