Re: might a bug in ido-mode

[zwz <zhangweize@gmail.com>]

Andreas Schwab <schwab@linux-m68k.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Instead of typing "c", type "bt" and show the results.  Please do that
>> in all of the 4 threads you have, like this:
>>
>>   (gdb) thread 1
>>   (gdb) bt
>>   (gdb) thread 2
>>   (gdb) bt
>>
>> etc.
>
> or
>
> (gdb) thread apply all bt
>
> Andreas.

Ok. Here is the output:
Thread 3 (thread 4136.0xa80):
#0  0x77cf5e74 in ntdll!LdrAccessResource ()
    from C:\windows\system32\ntddl.dll
#1  0x77cf5610 in ntdll!ZwWaitForMultipleObjects32 ()
    from C:\windows\system32\ntddl.dll
#2  0x7672a5d7 in WaitForMultipleObjectsEx ()
    from C:\windows\system32\kernel32.dll
#3  0x00000002 in ?? ()
#4  0x21dafef0 in ?? ()
#5  0x7672a6f0 in WaitForMultipleObjects ()
    from C:\windows\system32\kernel32.dll
#6  0x6e2d1883 in msiltcfg!ShutdownMsi ()
    from C:\windows\system32\msiltcfg.dll
#7  0x00000002 in ?? ()
#8  0x21daff78 in ?? ()
#9  0x7672d0e9 in KERNEL32!AcquireSRWLockExclusive ()
    from C:\windows\system32\kernel32.dll
#10 0x77cd19bb in ntdll!RtlInitializeNtUserPfn ()
    from C:\windows\system32\ntddl.dll
#11 0x77cd198e in ntdll!RtlInitializeNtUserPfn ()
    from C:\windows\system32\ntddl.dll
#12 0x00000000 in ?? ()

Thread 2 (thread 4136.0x1148):
#0  0x77cf5e74 in ntdll!LdrAccessResource ()
    from C:\windows\system32\ntddl.dll
#1  0x76aed67f in setjmp () from C:\windows\system32\msvcrt.dll
#2  0x0082ffc4 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (thread 4136.0xea8):
#0  0x77cf5e74 in ntdll!LdrAccessResource ()
    from C:\windows\system32\ntddl.dll
#1  0x764a6fd1 in USER32!SetMenuContextHelpId ()
    from C:\windows\system32\user32.dll
#2  0x0116e2fe in set_frame_menubar ()
#3  0x010178ef in update_menu_bar ()
#4  0x0102ad6a in prepare_menu_bars ()
#5  0x0102ed02 in redisplay_internal ()
#6  0x01061d66 in read_char ()
#7  0x01063334 in read_key_sequence.clone.0 ()
#8  0x01065bd0 in command_loop_1 ()
#9  0x0100a592 in internal_condition_case ()
#10 0x0105bebf in command_loop_2 ()
#11 0x0100a4dc in internal_catch ()
#12 0x0105c848 in command_loop ()
#13 0x0105c8d3 in recursive_edit_1 ()
#14 0x0104c8ce in Frecursive_edit ()
#15 0x01002d86 in main ()

I am using gdb 7.1.
p.s. Is there anyway to print the backtract to a file?

I want to give another description of how I catch the bug.
After C-x C-f, and input a file name, usually the ido-mode will try to
search in other directories if such a file exists, and says in the
minibuffer "searching for blabal ...". Now it is the very timing to hit
C-j or backspace. I find it is easier to catch the bug by backspace.
Anyway, I have to try many times in different directories with various
file names (which should be found by ido-mode in another directory other
than the current one) to catch the bug.

Hope this helps.