Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. C#
  4. Way to monitor API calls of programs?

Way to monitor API calls of programs?

Scheduled Pinned Locked Moved C#
windows-adminjsonquestion
6 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    bbranded
    wrote on last edited by
    #1

    Hello, Beyond monitoring registry, file system, etc access with process monitor, and window messages with the likes of something like Winspector, is there a piece of software that can watch API calls of processes? Thanks, Matt

    G 1 Reply Last reply
    0
    • B bbranded

      Hello, Beyond monitoring registry, file system, etc access with process monitor, and window messages with the likes of something like Winspector, is there a piece of software that can watch API calls of processes? Thanks, Matt

      G Offline
      G Offline
      Garth J Lancaster
      wrote on last edited by
      #2

      I was tempted to say .. 'look at Detours' qv http://research.microsoft.com/en-us/projects/detours/[^], but that doesnt help you in a C# environment AND I think you'd still have to know what API calls you were going to watch ahead of time .. so Im sorry, this is a waste of a post - I hope someone else has useful info for you .. 'g'

      B 1 Reply Last reply
      0
      • G Garth J Lancaster

        I was tempted to say .. 'look at Detours' qv http://research.microsoft.com/en-us/projects/detours/[^], but that doesnt help you in a C# environment AND I think you'd still have to know what API calls you were going to watch ahead of time .. so Im sorry, this is a waste of a post - I hope someone else has useful info for you .. 'g'

        B Offline
        B Offline
        bbranded
        wrote on last edited by
        #3

        That's very interesting, and brings up the point that the senior dev at my work said... detour/redirect the APIs. I think that process monitor actually attaches a debugger to each process, this isn't enough? What about analyzing the call stack (like process explorer), but in an on going logging manner? Thanks, Matt [ud] eyyy yo[^]

        modified on Friday, March 20, 2009 8:21 PM

        G 1 Reply Last reply
        0
        • B bbranded

          That's very interesting, and brings up the point that the senior dev at my work said... detour/redirect the APIs. I think that process monitor actually attaches a debugger to each process, this isn't enough? What about analyzing the call stack (like process explorer), but in an on going logging manner? Thanks, Matt [ud] eyyy yo[^]

          modified on Friday, March 20, 2009 8:21 PM

          G Offline
          G Offline
          Garth J Lancaster
          wrote on last edited by
          #4

          bbranded wrote:

          What about analyzing the call stack (like process explorer), but in an on going logging manner?

          ok, I could see this being used for exploratory purposes/during development, but, 'on going' ... surely it would be very expensive cpu-wise ? Interesting issue though .. does tickle something in the reccesses of my deep/gutter like brain .. something about someone with an instrumentation API for C# - but it wasnt making him/them any money so I think it got canned .. lets see... well, it wasnt this http://tracetool.sourceforge.net/[^] I was thinking of, but it may give you ideas ... 'g'

          B 1 Reply Last reply
          0
          • G Garth J Lancaster

            bbranded wrote:

            What about analyzing the call stack (like process explorer), but in an on going logging manner?

            ok, I could see this being used for exploratory purposes/during development, but, 'on going' ... surely it would be very expensive cpu-wise ? Interesting issue though .. does tickle something in the reccesses of my deep/gutter like brain .. something about someone with an instrumentation API for C# - but it wasnt making him/them any money so I think it got canned .. lets see... well, it wasnt this http://tracetool.sourceforge.net/[^] I was thinking of, but it may give you ideas ... 'g'

            B Offline
            B Offline
            bbranded
            wrote on last edited by
            #5

            I don't mean "on going," like on going, but more like how you'd use process monitor. Process explorer's call stack thing is very small, and simple. I'm looking to passively observe, and am looking for a piece of software, although an API is cool too. I'm not particularly looking for a debugger, as I can't debug software I may need to monitor (I work at a hedge fund, and am a net and sys admin, but I do code in C#). Are you speaking of fastice, or whatever that debugger is? Thanks for the replies! Matt

            G 1 Reply Last reply
            0
            • B bbranded

              I don't mean "on going," like on going, but more like how you'd use process monitor. Process explorer's call stack thing is very small, and simple. I'm looking to passively observe, and am looking for a piece of software, although an API is cool too. I'm not particularly looking for a debugger, as I can't debug software I may need to monitor (I work at a hedge fund, and am a net and sys admin, but I do code in C#). Are you speaking of fastice, or whatever that debugger is? Thanks for the replies! Matt

              G Offline
              G Offline
              Garth J Lancaster
              wrote on last edited by
              #6

              bbranded wrote:

              Are you speaking of fastice, or whatever that debugger is?

              no, there was an instrumentation api/product out there - cant find it now :-( 'g'

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups