migosh

Show:

What's happening?

  • Comment: Attach monitors on CreateProcess

    Unfortunately, I don't think I'll have time to implement this feature soon. When writing an automatic unittest it should be fairly easy to load the DLL explicitely, and programatically call all start/stop functions. If you'll need any support in using/understanding existing code, I'll be glad to help. Michael.

    2009-04-21 17:44:31 UTC in Windows Leaks Detector

  • Followup: RE: Debugging with WinLeak

    Hi Graham, The tool does not provide the direct measure of "rate" of the leaks, but tells you how many bytes were allocated from each call stack, and how many times did it happen. If it always shows only 2 call stacks, it's possible that the tool can't find additional causes to the memory leak. You can show me the output file, and I can try to help you with understanding the...

    2008-04-07 11:03:29 UTC in Windows Leaks Detector

  • Followup: RE: Can't work on Windows XP x64

    It would be great if you could help me with x64 support. You can see the source code (Code -> Browse), or you can download it in ZIP. So you can just send me the new files if you'll do any changes, and I will commit it to CVS. There's also an option to add you to the project as "developer" - so you'll have a direct access to the CVS repository, if you want. Let me know if you...

    2007-12-27 09:34:04 UTC in Windows Leaks Detector

  • Followup: RE: Can't work on Windows XP x64

    Hi Mike, This tool was never tested on x64 system, and from what you're saying - it just doesn't work... I don't believe I can add x64 support in a short time, maybe I'll look at it later. Sorry, Michael.

    2007-12-27 09:16:49 UTC in Windows Leaks Detector

  • Followup: RE: Welcome to Help

    I'm glad you could finally use the tool. According to the stack I guess that it's the internal allocation of the buffer made by std::cin to read data from the console, so it's not a leak. And, more important, even if you'll use make more allocations, or will do more "getc" calls, the size of this "leak" will not change.

    2007-12-24 05:17:57 UTC in Windows Leaks Detector

  • Followup: RE: Welcome to Help

    I'm sorry, that was my mistake - please don't use version 1.1.2, it contains incompatible files. New version (1.1.3) is available, I tested it with number of applications, and it worked. Hope this time it will be OK.

    2007-12-17 16:01:46 UTC in Windows Leaks Detector

  • Followup: RE: comdlg32.ocx

    Hi, I've uploaded a new version, which is not requiring this OCX, please try to use it and let me know if you are still getting some errors. Michael.

    2007-12-15 22:58:23 UTC in Windows Leaks Detector

  • Windows Leaks Detector

    migosh committed patchset 3 of module WEB to the Windows Leaks Detector CVS repository, changing 2 files.

    2006-11-21 19:45:37 UTC in Windows Leaks Detector

  • Windows Leaks Detector

    migosh committed patchset 3 of module MemoryHooks to the Windows Leaks Detector CVS repository, changing 3 files.

    2006-03-25 03:18:56 UTC in Windows Leaks Detector

  • Followup: RE: Whats next...

    I read the documents. I can understand the definition of the _drivers struct, and the user API for the drivers. Still I don't fully understand the internal implementation. For example, from "kbd.c": static void keyboard_irq(void) { unsigned scan_code, temp; scan_code = inportb(0x60); temp = convert(scan_code); device_data=temp; if(temp != 0) putch(temp);...

    2006-03-25 03:00:31 UTC in Meganet OS-3

About Me

  • 2006-02-28 (4 years ago)
  • 1463456
  • migosh (My Site)
  • migosh

Send me a message