all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6413@debbugs.gnu.org
Subject: bug#6413: What does ntdll!DbgUiConnectToDbg mean? (on w32)
Date: Sun, 13 Jun 2010 21:10:34 +0300	[thread overview]
Message-ID: <834oh6kdlx.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTik8aqqlq419yCUgDFmDOsG7ujYenq6UsbzqO-5A@mail.gmail.com>

> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Sun, 13 Jun 2010 18:58:25 +0200
> Cc: 
> 
> I just got this from the gdb running Emacs:
> 
> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 372.0xcec]
> 0x7c90120f in ntdll!DbgUiConnectToDbg () from C:\WINDOWS\system32\ntdll.dll
> (gdb) bt
> #0  0x7c90120f in ntdll!DbgUiConnectToDbg ()
>    from C:\WINDOWS\system32\ntdll.dll
> #1  0x7c951e40 in ntdll!KiIntSystemCall () from C:\WINDOWS\system32\ntdll.dll
> #2  0x00000005 in ?? ()
> #3  0x00000004 in ?? ()
> #4  0x00000001 in ?? ()
> #5  0x215affd0 in ?? ()
> #6  0x00000000 in ?? ()
> (gdb) c
> 
> Is there anything I can do to look into it further?

Try "info threads".  I'm guessing you will see a couple more threads,
in which case switch to each one of them and type "bt" to see their
call-stack.





  reply	other threads:[~2010-06-13 18:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13 16:58 bug#6413: What does ntdll!DbgUiConnectToDbg mean? (on w32) Lennart Borgman
2010-06-13 18:10 ` Eli Zaretskii [this message]
2011-07-03 18:49 ` Juanma Barranquero
2011-07-03 22:39   ` Lennart Borgman
2011-07-03 22:54     ` Juanma Barranquero
     [not found]       ` <CANbX365Yq49+iimQSejWU3K+zUrzpdf96UDJbO1vnE3TDM7stg@mail.gmail.com>
2011-07-03 23:05         ` Juanma Barranquero
2011-07-03 23:19           ` Lennart Borgman
2011-07-03 23:29             ` Juanma Barranquero
2011-07-03 23:44               ` Lennart Borgman
2011-07-04  0:34                 ` Juanma Barranquero

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=834oh6kdlx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=6413@debbugs.gnu.org \
    --cc=lennart.borgman@gmail.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.