voroojax / ospy

Automatically exported from code.google.com/p/ospy
0 stars 0 forks source link

Can't attach to any process #15

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Try to attach to any processes

What is the expected output? What do you see instead?
I receive this error message : 
---------------------------
Error
---------------------------
Failed to start capture: Method not found: 'Int32 
System.Threading.WaitHandle.WaitAny(System.Threading.WaitHandle[], Int32)'.

If you're trying to monitor Internet Explorer, make sure you disable its 
"Protected Mode" feature. This issue will be addressed in a future oSpy 
release.
---------------------------
OK   
---------------------------

What version of the product are you using? On what operating system?
1.10.2 Windows Vista Ultimate

Please provide any additional information below.
I've never been able to use the product at all, so I have little more to 
offer

Original issue reported on code.google.com by trex...@gmail.com on 26 Aug 2009 at 3:42

GoogleCodeExporter commented 9 years ago
Nice catch! Turns out that I'm using API only available from .NET Framework 2.0 
SP2. 
This is very trivial to fix, and I'll make sure the fix goes into 1.10.3. In 
the 
meantime, as a workaround, you could install:
http://www.microsoft.com/downloads/details.aspx?familyid=5B2C0358-915B-4EB5-9B1D
-
10E506DA9D0F&displaylang=en

I'll keep you posted. Thanks for the bug report!

Original comment by ole...@gmail.com on 26 Aug 2009 at 4:07

GoogleCodeExporter commented 9 years ago

Original comment by ole...@gmail.com on 26 Aug 2009 at 4:08

GoogleCodeExporter commented 9 years ago
Thank you... For now, I'll install that.

Original comment by trex...@gmail.com on 26 Aug 2009 at 4:57

GoogleCodeExporter commented 9 years ago
It actually says it is not supported on Vista when I try to install.  Guess I 
get to
wait!

Original comment by trex...@gmail.com on 26 Aug 2009 at 4:58

GoogleCodeExporter commented 9 years ago
Ah sorry, I didn't read the part about supported OSes. This one should provide 
what you 
need:
http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319
-
81da479ab0d7&displaylang=en
(Microsoft .NET Framework 3.5 Service Pack 1, which includes 2.0 SP2.)

Original comment by ole...@gmail.com on 26 Aug 2009 at 6:23

GoogleCodeExporter commented 9 years ago
Thanks.... I'm running windows update at the moment... and I think it is 
including
that.  I'll let you know how it goes!

Original comment by trex...@gmail.com on 26 Aug 2009 at 6:29

GoogleCodeExporter commented 9 years ago
Great! Just fixed this issue in HEAD:
http://code.google.com/p/ospy/source/detail?r=583

Just a few extra fixes and I'll release 1.10.3.

Original comment by ole...@gmail.com on 26 Aug 2009 at 9:05

GoogleCodeExporter commented 9 years ago
It is working for me now.  Thank you!

Original comment by trex...@gmail.com on 26 Aug 2009 at 9:13

GoogleCodeExporter commented 9 years ago
Today I updated my .NET framework to 3.5 ( w/ windows update ) on winXP ( to 
solve
this issue), and now I get another error when I try to attach to a process.
Details attached.

P.S: Still interested in a custom site and the collaboration part? I'm still
interested in working on it, if it'll be used.

//jinzo

Original comment by matjaz.c...@gmail.com on 26 Aug 2009 at 9:15

Attachments:

GoogleCodeExporter commented 9 years ago
trex005: Awesome! Thanks a lot for the bug report!

jinzo: Hey! Thanks for that one, looks like you've been unlucky. :) I've added 
code 
to detect and explain this issue in 1.10.3 just released, including 
instructions on 
how to fix it. (An automatic solution will be provided in a future release.) 
It's 
basically that oSpy (or actually EasyHook to be precise) temporarily registers 
some 
.NET libraries in the system's GAC (Global Assembly Cache) and spawns a service 
that 
sits and monitors the lifetime of the oSpy process, and as soon as oSpy goes 
away the 
service will undo the changes to the system. Only problem is if this service 
gets 
killed by the user (unlikely), or the system gets shutdown in an unclean manner 
(like 
power failure on a desktop machine without UPS), there will be three libraries 
left 
in the GAC. Would be great if you could try out the new version and follow the 
instructions there, and let me know if it works. (Preferably in a separate 
"issue" so 
I can keep track of it more easily. :) )

Definitely interested in getting a proper site up and running with 
collaboration 
support, so that's much appreciated! I'll see if I can come up with a hosting 
provider, a friend of mine was going to host it but it looks like he's busy 
these 
days so I think I'll look for something else. :)

Cheers,
Ole André

Original comment by ole...@gmail.com on 27 Aug 2009 at 1:31