all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: 13700@debbugs.gnu.org
Subject: bug#13700: Program received signal SIGTRAP, Trace/breakpoint trap
Date: Wed, 13 Feb 2013 05:49:05 +0200	[thread overview]
Message-ID: <83vc9w50we.fsf@gnu.org> (raw)
In-Reply-To: <86621x8be4.fsf@somewhere.org>

> From: "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com>
> Cc: 13700@debbugs.gnu.org
> Date: Tue, 12 Feb 2013 22:34:11 +0100
> 
> >> Program received signal SIGTRAP, Trace/breakpoint trap.
> >> [Switching to Thread 15276.0x5d48]
> >> 0x77af2fac in ntdll!RtlVerifyVersionInfo () from
> >> /cygdrive/c/Windows/SYSTEM32/ntdll.dll
> >
> > This is normal.  On Windows, the F-12 key breaks into the debugger,
> > which is what you see.
> 
> Just got a segmentation fault (and Emacs 24.2.93 crashed) when answering you
> to this post. See next post.
> 
> My question was: can I ignore those, because it forces me to go to the GDB
> terminal (and to type "continue") each time I'm pressing F12, which is a
> lot...

Just don't press F12.





  reply	other threads:[~2013-02-13  3:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 18:38 Program received signal SIGTRAP, Trace/breakpoint trap Sebastien Vauban
2013-02-12 20:53 ` bug#13700: " Eli Zaretskii
2013-02-13 18:37   ` Glenn Morris
2013-02-13 19:29     ` Achim Gratz
2013-02-13 19:40       ` Glenn Morris
     [not found] ` <mailman.19712.1360702421.855.bug-gnu-emacs@gnu.org>
     [not found]   ` <mailman.19712.1360702421.855.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-02-12 21:34     ` Sebastien Vauban
2013-02-13  3:49       ` Eli Zaretskii [this message]
     [not found]       ` <mailman.19764.1360727379.855.bug-gnu-emacs@gnu.org>
     [not found]         ` <mailman.19764.1360727379.855.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-02-13  8:25           ` Sebastien Vauban

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83vc9w50we.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13700@debbugs.gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.