Re: might a bug in ido-mode

[zwz <zhangweize@gmail.com>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: zwz <zhangweize@gmail.com>
>> Date: Mon, 26 Apr 2010 19:27:24 +0800
>> 
>> and then I tried the step 3 and 4 many times with various file names
>> (e.g. main.c, test.c, etc.). Here the most important thing is that you
>> should try to hit C-j when the ido-mode is searching. The timing is the
>> key to catch the bug.
>
> I didn't succeed in doing that, ido is too fast on my machine.

When I am using ido, I can see "searching for main.cpp ..." in the
minibuffer, and then I try to hit the C-j, or backspace to catch the bug.

>
>> the gdb console says:
>> gdb: unknown target exception 0xc0000029 at 0x77d10754
>> program received signal ?, unknown signal.
>
> What version of GDB is that? what does "gdb --version" display?

I am using GDB 7.1.

>
>> [switch to thread 5860.0xa80]
>> 0x77d10754 in ntdll!EtwpNotificationThread()
>>     from C:\Windows\system32\ntdll.dll
>> (gdb) warning: Invalid parameter passed to C runtime function. (9 times)
>> 
>> And after I input "c" to continue the program, emacs crashes, with
>> the gdb console saying:
>> program exited with code 030000000051
>
> 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.
>
> Thanks.