* bug#6413: What does ntdll!DbgUiConnectToDbg mean? (on w32)
@ 2010-06-13 16:58 Lennart Borgman
2010-06-13 18:10 ` Eli Zaretskii
2011-07-03 18:49 ` Juanma Barranquero
0 siblings, 2 replies; 10+ messages in thread
From: Lennart Borgman @ 2010-06-13 16:58 UTC (permalink / raw)
To: 6413
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? I can't think of
anything I did in Emacs this time that triggered this so I am a bit
lost.
As I previously mentioned I have added a macro to test system calls
return values and I wonder if this somehow is involved here or if this
is just one of these "doctor watson-crashes" I now and then see, as
seen through gdb.
The macro I added just looks like
#define W32ASSERT(TEST, WHERE) if (!TEST) DebPrint (("%s: %s\n",
WHERE, w32_strerror(0)))
In the code I write this as something like
W32ASSERT (0, "w32_SetWindowPos_from_main_thread.PostMessage");
or with 0 replaced by a variable.
This does not look problematic too me, but I wonder if DepPrint can be
called anywhere. Is there some problem calling it inside a BLOCK_INPUT
.. UNBLOCK_INPUT?
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#6413: What does ntdll!DbgUiConnectToDbg mean? (on w32)
2010-06-13 16:58 bug#6413: What does ntdll!DbgUiConnectToDbg mean? (on w32) Lennart Borgman
@ 2010-06-13 18:10 ` Eli Zaretskii
2011-07-03 18:49 ` Juanma Barranquero
1 sibling, 0 replies; 10+ messages in thread
From: Eli Zaretskii @ 2010-06-13 18:10 UTC (permalink / raw)
To: Lennart Borgman; +Cc: 6413
> 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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#6413: What does ntdll!DbgUiConnectToDbg mean? (on w32)
2010-06-13 16:58 bug#6413: What does ntdll!DbgUiConnectToDbg mean? (on w32) Lennart Borgman
2010-06-13 18:10 ` Eli Zaretskii
@ 2011-07-03 18:49 ` Juanma Barranquero
2011-07-03 22:39 ` Lennart Borgman
1 sibling, 1 reply; 10+ messages in thread
From: Juanma Barranquero @ 2011-07-03 18:49 UTC (permalink / raw)
To: Lennart Borgman; +Cc: 6413
On Sun, Jun 13, 2010 at 18:58, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
> Is there anything I can do to look into it further? I can't think of
> anything I did in Emacs this time that triggered this so I am a bit
> lost.
Is this bug repeatable, or can we close it?
Juanma
^ permalink raw reply [flat|nested] 10+ messages in thread
* bug#6413: What does ntdll!DbgUiConnectToDbg mean? (on w32)
2011-07-03 18:49 ` Juanma Barranquero
@ 2011-07-03 22:39 ` Lennart Borgman
2011-07-03 22:54 ` Juanma Barranquero
0 siblings, 1 reply; 10+ messages in thread
From: Lennart Borgman @ 2011-07-03 22:39 UTC (permalink / raw)
To: Juanma Barranquero; +Cc: 6413
On Sun, Jul 3, 2011 at 20:49, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Sun, Jun 13, 2010 at 18:58, Lennart Borgman
> <lennart.borgman@gmail.com> wrote:
>
>> Is there anything I can do to look into it further? I can't think of
>> anything I did in Emacs this time that triggered this so I am a bit
>> lost.
>
> Is this bug repeatable, or can we close it?
I saw some more of this, but at the moment I have no setup to repeat it.
You might look at the macro. I would be glad for some comments on it
since I rarely right code like that.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2011-07-04 0:34 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-13 16:58 bug#6413: What does ntdll!DbgUiConnectToDbg mean? (on w32) Lennart Borgman
2010-06-13 18:10 ` Eli Zaretskii
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
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.