bug#15024: 24.3; Crash when editing pattern for Helm-for-files

["Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>]

Eli Zaretskii wrote:
>> From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
>> Cc: 15024-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org
>> Date: Mon, 12 Aug 2013 11:14:19 +0200
>> 
>> When displaying a PDF file (via DocView -- it worked), got this when killing
>> the buffer[1] IIRC:
>> 
>> --8<---------------cut here---------------start------------->8---
>> [Thread 11448.0x2c1c exited with code 0]
>> [New Thread 11448.0x2bc4]
>> gdb: Target exception EXCEPTION_BREAKPOINT at 0xe4311e00
>> 
>> Program received signal SIGTRAP, Trace/breakpoint trap.
>> [Switching to Thread 11448.0x2bc4]
>> 0x775c2d3c in ?? ()
>> (gdb) bt
>> #0  0x775c2d3c in ?? ()
>> (gdb)
>> --8<---------------cut here---------------end--------------->8---
>> 
>> Is this what you need?
>
> No, this is false alarm.  F12 causes an immediate break into the
> debugger on Windows.

OK.

> Can you temporarily undo the F12 binding?  You can always type
> "continue" when this happens, but it would be a nuisance for you to
> remember to do that every time.

Yes, this is a real nuisance...

Is there a way to unbind F12 from breaking into the debugger on Windows?
Something in .gdbinit or so?  If possible, I'd like to keep using F12 in Emacs
-- that key binding is hardcoded in my brain...

Thanks for your help so far!

Best regards,
  Seb

-- 
Sebastien Vauban