I'm getting this AV in EDB Manager (Unicode) 202b10 frequently (the
address is always the same):

Access violation at address 006C5AAC in module 'edbmgr.exe'. Read of
address 00000000.

When it happens, edbmgr.exe has to be killed by the task manager.
Curiously, dragging any other window over edbmgr's right-hand pane at
this time will generate a slew of identical AV dialogs.

I don't know a consistent way to cause it, but the AV usually appears
while opening/closing nodes in the left-hand pane of edbmgr, and only
after creating one or more local sessions.

I don't know if it's useful, but here's the stack of the process's only
thread after an AV (as reported by Process Explorer):

Thread edbmgr.exe+0x2cd3ec

ntkrnlpa.exe+0x6dc0b
ntkrnlpa.exe!MmIsDriverVerifying+0xa30
ntkrnlpa.exe!MmIsDriverVerifying+0x1312
win32k.sys+0x2f40
win32k.sys+0x3746
win32k.sys+0x3763
ntdll.dll!KiFastSystemCallRet
USER32.dll!DrawStateW+0x1f2
USER32.dll!SoftModalMessageBox+0x677
USER32.dll!MessageBoxIndirectA+0x23a
USER32.dll!MessageBoxTimeoutW+0x7a
USER32.dll!MessageBoxExW+0x1b
USER32.dll!MessageBoxW+0x45
edbmgr.exe+0xc86b2
edbmgr.exe+0xc8804
edbmgr.exe+0xc8593
edbmgr.exe+0x3061a
USER32.dll!GetDC+0x6d
USER32.dll!GetDC+0x14f
USER32.dll!GetParent+0x16c
USER32.dll!SendMessageW+0x49
comctl32.dll!Ordinal414+0xfb4
comctl32.dll!Ordinal341+0x60
comctl32.dll!Ordinal384+0x2bfd7
comctl32.dll!Ordinal384+0x31e64
comctl32.dll!Ordinal384+0x32e0a
comctl32.dll!Ordinal384+0x3571e
USER32.dll!GetDC+0x6d
USER32.dll!GetDC+0x14f
USER32.dll!IsWindowUnicode+0xa1
USER32.dll!CallWindowProcW+0x1b
edbmgr.exe+0xabb04
edbmgr.exe+0x818da
edbmgr.exe+0xaba08
edbmgr.exe+0x8006d
edbmgr.exe+0x3061a
USER32.dll!GetDC+0x6d
USER32.dll!GetDC+0x14f
USER32.dll!DefWindowProcW+0x184
USER32.dll!DefWindowProcW+0x1d0
ntdll.dll!KiUserCallbackDispatcher+0x13
USER32.dll!DispatchMessageW+0xf
USER32.dll!CallMsgFilterW+0x213
USER32.dll!DrawStateW+0x1f2
USER32.dll!SoftModalMessageBox+0x677
USER32.dll!MessageBoxIndirectA+0x23a
USER32.dll!MessageBoxTimeoutW+0x7a
USER32.dll!MessageBoxExW+0x1b
USER32.dll!MessageBoxW+0x45
edbmgr.exe+0xc86b2
edbmgr.exe+0xc8804
edbmgr.exe+0xc8593
edbmgr.exe+0x3061a
USER32.dll!GetDC+0x6d
USER32.dll!GetDC+0x14f
USER32.dll!GetParent+0x16c
USER32.dll!SendMessageW+0x49
comctl32.dll!Ordinal414+0xfb4
comctl32.dll!Ordinal341+0x60
comctl32.dll!Ordinal341+0x9d
comctl32.dll!Ordinal384+0x4eb6f
comctl32.dll!Ordinal384+0x51820
comctl32.dll!Ordinal384+0x518bd
comctl32.dll!Ordinal384+0x31587
comctl32.dll!Ordinal384+0x33ed8
comctl32.dll!Ordinal384+0x35bb9
USER32.dll!GetDC+0x6d
USER32.dll!GetDC+0x14f
USER32.dll!IsWindowUnicode+0xa1
USER32.dll!CallWindowProcW+0x1b
edbmgr.exe+0xabb04
edbmgr.exe+0xaba08
edbmgr.exe+0x8006d
edbmgr.exe+0x3061a
USER32.dll!GetDC+0x6d
USER32.dll!GetDC+0x14f
USER32.dll!GetParent+0x16c
USER32.dll!SendMessageW+0x49
edbmgr.exe+0x7c2da

Me too - same error. If I hold down the escape key it powers through all the
exceptions and then it seems to work ok. For me it seems to happen whenever
I add a new Session or a new Database to a session.

Charles,

<< I'm getting this AV in EDB Manager (Unicode) 202b10 frequently (the
address is always the same):

Access violation at address 006C5AAC in module 'edbmgr.exe'. Read of
address 00000000.

When it happens, edbmgr.exe has to be killed by the task manager.
Curiously, dragging any other window over edbmgr's right-hand pane at this
time will generate a slew of identical AV dialogs. >>

We've had another report of this, but have been unable to reproduce it at
all.  It doesn't happen on every machine apparently, and doesn't happen here
at all.

I'll keep checking this out and see what I can find.

--
Tim Young
Elevate Software
www.elevatesoft.com

Charles,

One other question:

Are you using the Unicode EDB Manager ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Yes - Unicode EDB Manager on WinXP x64.

Yes, Unicode.

Tim Young [Elevate Software] wrote:
> Charles,
>
> One other question:
>
> Are you using the Unicode EDB Manager ?
>
..

Charles,

<< Yes, Unicode. >>

Okay, I found out the problem and a fix will be in 2.02 B11 due out next
week.

--
Tim Young
Elevate Software
www.elevatesoft.com