GNU bug report logs -
#15024
24.3; Crash when editing pattern for Helm-for-files
Previous Next
Full log
Message #58 received at 15024 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii wrote:
>> From: "Sebastien Vauban" <sva-news <at> mygooglest.com>
>> Cc: 15024 <at> debbugs.gnu.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
This bug report was last modified 11 years and 178 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.