D 2.0 Stacktrace - similar problems

Benjamin Thaut code at benjamin-thaut.de
Thu Oct 7 23:46:51 PDT 2010


Am 08.10.2010 03:16, schrieb Austin Hastings:
> On 10/6/2010 4:00 PM, Yao G. wrote:
>> I forgot to mention. I'm compiling the file using:
>>
>>> dmd test.d C:\dmd\src\stacktrace.d C:\dmd\src\dbghelp.d -g -w
>>
>
> I have a similar problem as Yao.
>
> I've got XP SP3/x86 with dbghelp.dll version 5.1.2600.5512 in the
> windows\system32 directory.
>
> I copied dbghelp.dll version 6.12.2.633 from a recent install of
> Debugging Tools for Windows (x86) into the directory with the stacktrace
> sources.
>
> $ ls -alG
> total 1211
> drwxr-xr-x 2 Austin 0 Oct 7 21:12 .
> drwxr-xr-x 3 Austin 0 Oct 7 20:11 ..
> -rw-r--r-- 1 Austin 9020 Oct 7 21:04 dbghelp.d
> -rwxr-xr-x 1 Austin 1213200 Oct 7 20:21 dbghelp.dll
> -rw-r--r-- 1 Austin 1331 Oct 7 20:11 licence.txt
> -rw-r--r-- 1 Austin 1277 Oct 7 20:11 readme.txt
> -rw-r--r-- 1 Austin 11335 Oct 7 20:11 stacktrace.d
> -rw-r--r-- 1 Austin 90 Oct 7 20:11 test.d
>
> I compile using:
>
> $ dmd -g -w test.d stacktrace.d dbghelp.d
>
> which succeeds no problem. I put code in to check the result of the
> loadLibrary call, and it reports:
>
> Got valid dll handle
> Path: d:\devel\d\libs\src\stacktrace\dbghelp.dll
>
> So the right version is being opened. But I still get:
>
> object.Exception: Test
> ----------------
> 00 4223864
> 01 4223927
> 02 4223617
> 03 4439269
> 04 RegisterWaitForInputIdle
>
> I'm fairly certain I meet all the basic requirements: compile with -g
> for debug info, copy a late version of dbghelp.dll into application
> directory. But I'm getting the InputIdle failure, which acts like it
> doesn't matter.
>
> Is there an upper limit on the dbghelp.dll version? I notice that Yao
> reported using 6.7.5, while 6.12 is leading edge. What version are you
> using, Benjamin?
>
> Thanks in advance for any help, I'm really looking forward to using this
> module.
>
> =Austin
Hm I don't have  a XP machine to test on. But as Symbol 04 is resolved, 
it seems to work. It just can not resolve symbols inside your 
application. There is no upper limit to dbghelp.dll. I'm on Windows 7 
with dbghelp version 6.1.7600.16385. Most likely the probelm are the CV 
debugging symbols, as it was kind of hacky to get it to read those. Try 
converting your application with cv2pdb to pdb debugging symbols and see 
if this fixes the problem.

-- 
Kind Regards
Benjamin Thaut


More information about the Digitalmars-d-announce mailing list