program creash on Japanese IME 2000

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi, Gary, I recompile my code under UICODE setting and it
seems that it still crashes under Janpanese Language
input. It is strange, it can run on that machine, but as
long as Japanese IME is up, it will creash my program
right away..

Any one know what else I am missing or something else
could cause the problem??

Thanks a lot. -- Haibo
 
Hello Haibo,

Thanks for posting in the group.

I also saw the former post from you. Based on my understanding, now the
problem is: When the input locale is English in the system, your
application could start or run well. However, if you change input locale to
Japanese, the application crashes whenever running or starting. Please post
here if I have misunderstood the problem.

It is really hard to isolate the problem based on the description. I don't
know Japanese. But based on my experience, this problem is not happening in
a Chinese system. I think you need to do the following troubleshooting
steps to isolate the problem:

1) Does this problem happen on other machines? If it is machine specific,
we need to pay more attention to machine instead of program.

2) When the crash happens, please click "retry" button to debug the
application and check the call stack. It may gives some idea on where the
problem resides. Also, visual studio 6.0 tools spy++ could log messages to
the application window.

3) Is there any special part in the application? Did you try to comment out
code slice to isolate the problem?

Hope that helps.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi, Here part of Dr. Waston's traces,

State Dump for Thread Id 0x9a8

eax=0000030d ebx=7ffde6cc ecx=00000000 edx=00160b11
esi=00000000 edi=0091030d
eip=75e70647 esp=0012dca4 ebp=0012dcb4 iopl=0 nv
up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038
gs=0000 efl=00000202


function: ImmGetImeMenuItemsW
75e70625 56 push esi
75e70626 57 push edi
75e70627 8855fc mov
[ebp+0xfc],dl ss:00d8b286=00
75e7062a 8bf9 mov edi,ecx
75e7062c 33f6 xor esi,esi
75e7062e 64a118000000 mov eax,fs:
[00000018] fs:00000018=????????
75e70634 8b0d0030e775 mov ecx,
[75e73000] ds:75e73000=00000000
75e7063a 8d98cc060000 lea ebx,
[eax+0x6cc] ds:000009d9=????????
75e70640 8bc7 mov eax,edi
75e70642 25ffff0000 and eax,0xffff
FAULT ->75e70647 3b4108 cmp eax,
[ecx+0x8] ds:00c5d5d2=????????
75e7064a 7359 jnb 75e791a5
75e7064c 8b0d4430e775 mov ecx,
[75e73044] ds:75e73044=00000000
75e70652 8d0440 lea eax,
[eax+eax*2] ds:0000030d=????????
75e70655 8d0c81 lea ecx,
[ecx+eax*4] ds:0000030d=????????
75e70658 8bc7 mov eax,edi
75e7065a c1e810 shr eax,0x10
75e7065d 663b410a cmp ax,
[ecx+0xa] ds:00c5d5d3=????
75e70661 740b jz 75e76c6e
75e70663 6685c0 test ax,ax
75e70666 7406 jz 75e76c6e
75e70668 663dffff cmp ax,0xffff

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4
Function Name
0012DCB4 75E67CF0 00160BF8 0012DCD8 75E679EF 0091030D
imm32!ImmGetImeMenuItemsW
0012DCC0 75E679EF 0091030D 0091030D 00160BF8 00000000
imm32!ImmLockClientImc
0012DCD8 75E67A9A 0091030D 00000001 72CDAB43 0091030D
imm32!ImmGetVirtualKey
0012DCF4 72CDB620 0091030D 0091030D 00160818 00000000
imm32!ImmLockIMC
0012DD20 72CDAF79 00160818 0012DD74 00000064 0091030D
imejp!ImeSelect
0012DD78 005B21DF 0091030D 00000001 0015F140 0015F130
imejp!ImeSelect
0012DD94 005B7A3C 0091030D E0010411 00000001 003601E2
imm32!ImmSetActiveContext
0012DDB4 005B7A9A 0091030D 00000001 005B1E62 0091030D
imm32!ImmGetVirtualKey
0012DDE4 77E57B2B 003601E2 00000000 00000001 0091030D
imm32!ImmLockIMC
0012E024 77E56B2E 00000000 00000287 00000017 003601E2
user32!IMPSetIMEA
0012E048 77E1558A 001F0170 00000287 00000017 003601E2
user32!IMPSetIMEA
0012E070 77F91A7F 0012E080 00000018 006923B8 00000287
user32!DefWindowProcA
0012E0AC 77E33247 0038025E 00000110 003601E2 0012E648
ntdll!KiUserCallbackDispatcher
0012E0E4 77E28B4B 77E33230 0038025E 00000110 003601E2
user32!MessageBoxA
0012E120 77E162DA 0038025E 00000110 003601E2 0012E648
user32!CharPrevW
0012E150 77E29C20 00663DF0 00000110 003601E2 0012E648
user32!IsWindowVisible
0012E208 77E43EAE 77E10000 00000006 00000000 00663DF0
user32!CharPrevW
0012E238 77E33F6A 77E10000 00134370 00000000 77E33230
user32!CheckRadioButton
0012E4F0 77E34306 00000030 0012E690 FFFFFFFF 00000030
user32!SoftModalMessageBox
0012E638 77E337FB 00000001 00000000 00000028 00000000
user32!MessageBoxExA
0012E690 77E34091 00000000 0015C088 00136810 00000030
user32!MessageBoxExW
0012E6C0 77E3322C 00000000 004A1260 01FD25D0 00000030
user32!MessageBoxExA
0012E6E0 00477068 00000000 004A1260 01FD25D0 00000030
user32!MessageBoxA
0012E818 004770B9 004A1260 00000000 00000000 0012FF10 !
<nosymbols>
0012E82C 004010A6 004A1260 00000000 00000000 004ADEF8 !
<nosymbols>
0012FF10 00475AC6 0012CA56 00000000 7FFDF000 0046D0E3 !
<nosymbols>
0012FFC0 77EA847C 0012CA56 0000000A 7FFDF000 C0000005 !
<nosymbols>
0012FFF0 00000000 0045D39F 00000000 000000C8 00000100
kernel32!ProcessIdToSessionId

why it will crash in ImmGetImeMenuItemsW ? Any idea? do I
need to sepcify the resource in Japanese?

Thanks.
 
Hello Haibo,

Thanks for the quick response.

We still can't find out the exact reason based on the Dr. Watson's log. I
observed that there are some MessageBoxA calles in the call stack. What is
it?

Also, could you please test on other machines to see if this problem
happens on them?

I don't think you need to specify resource in Japanse. For an example, if
we are running a purely English version of application on Win XP, when we
change input Locale to Chinese, surely the English application won't crash.
If we can't see Japanese characters correctly in the screen, we may think
of it as a Japanese resource problem.

For this question, I think we may need to analysis the application first to
find out where the problem may resides. A code debug may be the most direct
way to analyze it.

Thanks and please feel free to post here if you have any more concerns on
it.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi, Yanhong and Gary, Thanks for your help. I have found
the problem, basically it is the dll version problem. The
installation package mistakenly pack some system dlls and
put them into local folder and for some system, those
dlls are not compatible...

Thanks a lot for your help. -- Haibo
 
Hi Haibo,

So the problme should only happen on one machine. :) I am glad to hear that
the problem is resolved. If there are any questions, please feel free to
post in the group. It is our pleasure to be of assistance.

Thanks for participating the community.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top