Bug?

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #73
    Anonymous
    Participant

    VisualDDK Console ‘s command like “u IoDeleteDevice” can’t work well.

    u nt!IoDeleteDevice
    Type information missing error for IoDeleteDevice
    Couldn’t resolve error at ‘nt!IoDeleteDevice’

    but my symblos are no problem.
    !lmi nt
    Loaded Module Info: [nt]
    Module: ntkrnlpa
    Base Address: 804d8000
    Image Name: ntkrnlpa.exe
    Machine Type: 332 (I386)
    Time Stamp: 45e53f9c Wed Feb 28 16:38:52 2007
    Size: 1f6400
    CheckSum: 1facf5
    Characteristics: 12e
    Debug Data Dirs: Type Size VA Pointer
    CODEVIEW 25, 9540, 9540 RSDS – GUID: {F612363D-B38C-423C-B085-59DDBCA9F2F7}
    Age: 1, Pdb: ntkrnlpa.pdb
    Image Type: MEMORY – Image read successfully from loaded memory.
    Symbol Type: PDB – Symbols loaded successfully from symbol server.
    E:mysymbolsntkrnlpa.pdbF612363DB38C423CB08559DDBCA9F2F71ntkrnlpa.pdb
    Load Report: public symbols , not source indexed
    E:mysymbolsntkrnlpa.pdbF612363DB38C423CB08559DDBCA9F2F71ntkrnlpa.pdb

    another suggestion:
    Command automatically fill is useful,the ‘Tab’ can work in Windbg

    #995
    support
    Keymaster

    What does .symopt show in WinDbg and VisualDDK? If you set symbol options in VisualDDK equal to WinDbg ones, will the bug disappear? If you open Disassembly window in Visual Studio, and type IoCreateFile (should work even without nt! prefix there), does it locate the function correctly?

    #996
    Anonymous
    Participant

    kd> .symopt
    Symbol options are 0x30237:
    0x00000001 – SYMOPT_CASE_INSENSITIVE
    0x00000002 – SYMOPT_UNDNAME
    0x00000004 – SYMOPT_DEFERRED_LOADS
    0x00000010 – SYMOPT_LOAD_LINES
    0x00000020 – SYMOPT_OMAP_FIND_NEAREST
    0x00000200 – SYMOPT_FAIL_CRITICAL_ERRORS
    0x00010000 – SYMOPT_AUTO_PUBLICS
    0x00020000 – SYMOPT_NO_IMAGE_SEARCH

    .symopt
    Symbol options are 0x30233:
    0x00000001 – SYMOPT_CASE_INSENSITIVE
    0x00000002 – SYMOPT_UNDNAME
    0x00000010 – SYMOPT_LOAD_LINES
    0x00000020 – SYMOPT_OMAP_FIND_NEAREST
    0x00000200 – SYMOPT_FAIL_CRITICAL_ERRORS
    0x00010000 – SYMOPT_AUTO_PUBLICS
    0x00020000 – SYMOPT_NO_IMAGE_SEARCH

    Symbol search path is: SRV*E:mysymbols*http://msdl.microsoft.com/download/symbols(WinDBG)
    symbol options are same!
    type IoCreateFile in Disassembly window in Visual Studio work fine!

    #997
    support
    Keymaster

    I guess that the problem is caused by WinDbg using MASM syntax parser by default, and VisualDDK using C++ parser (switching it every time would be very slow). You can try using @@masm(nt!…), however, in the future versions, I’ll add automatic redirection to Disassembly window when the ‘u’ command is typed.
    Regarding the automatic command completion by ‘TAB’, is there any textfile, containing a list of all WinDbg commands? Parsing help files and rebuilding it could be quite inaccurate. If not, I’ll maybe add this support to next version, but provide only a sample command list file, encouraging users to update it.

    #998
    Anonymous
    Participant

    Thanks! use @@masm(nt!…) work very well.
    I think it is better to redirect these commands lik ‘u’,’bp’,’d’ and so on.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.