Problems with Distributed Objects [update]
Problems with Distributed Objects [update]
- Subject: Problems with Distributed Objects [update]
- From: Simone Manganelli <email@hidden>
- Date: Sat, 3 Jan 2004 00:29:33 -0800
OK, I've pinned down what's causing these error messages, but it's got
me completely baffled. What's happening is that I execute the helper
tool after authorization, and the parent application continues to
execute code. One of the lines of code that the parent application
executes is to get a string from the vended object (the parent app
itself is still vending that object), and then to set the value of that
string to a text field. But what's weird is that the error occurs
whenever that line is NOT in the code. It seems that maybe these lines
of code simply prevent the connection from being invalidate
prematurely. The thing is, I've tried retaining the vended object from
inside the parent app (in case it was accidentally released), and from
inside the helper tool that's accessing the vended object, but that
doesn't help at all. The error message implies that either the vended
object gets released or its connection gets invalidated, but I can't
see where that happens at all, because I'm not invalidating the
connection at all!
Can anyone help me with this problem?
-- Simone Manganelli
(original message follows)
One of my programs is consistently crashing when trying to access the
method of a distributed object, even though it used to work (and I'm
not exactly sure what made the problem happen). I post the
distributed object from one of my executables, which then launches a
helper tool and accesses the distributed object from the parent
application -- and it successfully accesses one of the methods in the
distributed object (which specifically retrieves an array from the
parent process), but then when it tries to run another method, my
program always crashes -- the method itself doesn't cause the crash,
but when the method called tries to access one of the instance
variables in that class, it isn't able to.
What's weird is that I know that the string that the method is trying
to access has a valid value -- I put in some logging functions, and
the string contents are what's expected: it's just that it crashes the
program when trying to access the instance variable through a
distributed object.
This is the error that I get when I run the program using ZeroLink
(under the standard "Development" build style): "ZeroLink: unknown
symbol '_objc_getClass'". This error message changes to "*** Uncaught
exception: <NSInvalidReceivePortException> connection went invalid
while waiting for a reply" when using the "Deployment" build style.
Does anybody know what could cause this and where to start debugging?
I've done numerous testing and I can't see any problems.
-- Simone Manganelli
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.