What WINDOWS CE debugging tools would you like to see?

  • Article

Just an informal survey -- I use some of our tools all the time, some rarely.  I have my own nitpicks I'd like fixed and features I'd like to see added.  But there's no guarantee I see the world the way you do.  What are your opinions?

Here are some ideas of my own, to get the conversation started:

  • Remote regedit: Export/import data under a key.  Track and report changes under a key.
  • Remote performance monitor: More counters!
  • Kernel profiler: UI in the remote tools menu in addition to the on-device control we already have.
  • Remote kernel tracker... don't even get me started, I love this tool but have lots of features I want added.  What would YOU ask for?
  • Does anybody use Remote Heap Walker??
  • I'd say we need to add a memory visualization tool that shows you what parts of the VM space are used -- something like "mi full" from the target control window.
  • I also think we need to add a handle enumerator -- eg. to find out what file handles are open (and by whom), window handles, etc.

Tell me what you think is most important!  What's the #1 debugging tool you wish you had?  What's the #1 feature our existing tools are missing?

Comments

  • Anonymous
    August 31, 2004
    REMOTE PROCESS ATTACH

    Really, with the amount of 3rd-party device driver development I do, as well as the Microsoft-mandated "resolution" for the process limit of moving you applications into service DLLs, I think the need to attach to a process on the device for debugging is absolutely critical to ISV developers like myself who don't have the ability to generate our own platforms.
  • Anonymous
    August 31, 2004
    Have you tried the "File>>Connect Network Registry" in the current regedit? It won't track and report changes but you should export /import remote keys.

    Certainly a tool that shows who has a file handle open would be useful (and even better if it has a choice to forcibly close the file). For finding who is locking a file I'm currently using Winternals' Process Explorer and doing searches but a tool that shows the files directly would be better.
  • Anonymous
    August 31, 2004
    two words. SoftIce and IDA. SoftIce so you guys can learn how to write a debugger independent of windows (ala windows crashes debugger still runs) and IDA so you guys can learn about interactive disassembly.

  • Anonymous
    August 31, 2004
    I guess I should have specified, I'm most interested in hearing about tools FOR WINDOWS CE, and OTHER THAN the debugger. (Yeah, asking about "debugging tools" without clarifying was pretty stupid.)

    Though I'll certainly pass CE debugger / tools comments on to our tools team. I can't do much about comments about desktop Windows.

    Sue
  • Anonymous
    September 01, 2004
    The comment has been removed
  • Anonymous
    September 06, 2004
    The comment has been removed
  • Anonymous
    September 08, 2004
    The comment has been removed