Re: Apple System Profiler & OT modules

Subject: Re: Apple System Profiler & OT modules
From: Quinn <email@hidden>
Date: Wed, 20 Jun 2001 14:59:40 +0100

At 19:13 +0200 15/6/01, Jean-Pierre wrote:

here's the MacsBug stack crawl:

Calling chain using A6/R1 links
Back chain ISA Caller
00000000 PPC 3B107198 0D0BB970 PPC 3B153C30 0D0BB810 PPC 3B0FD42C 0D0BB7B0 PPC 3B15ECC4 0D0BB760 PPC 3B0FCC8C 0D0BB700 PPC 3B0FCC1C 0D0BB6C0 PPC 3B0F1E50 0D0BB680 PPC 3B0F2C10 0D0BB600 PPC 3B15A678 0D0BB5C0 PPC 3B08D138 0D0BB580 PPC 3B08CF14 0D0BB540 PPC 3B099454 0D0BAA50 PPC 3B098B74 0D0BA9F0 PPC 3F6EF928 OTBind+00050
0D0BA9B0 PPC 3F6FB1CC OTOpenEndpointOnStreamPriv+0033C
0D0BA850 PPC 3F6F8148 TNativeProvider::WaitForSyncDone(StateRecord*)+00038
0D0BA810 PPC 3F6F4D64 TSTREAM::WaitForSignal()+00068
0D0BA7A0 PPC 3F72F6A4 OTNativeProcessKernelMsg+000F4

OK, from this log it's clear to see that the deadlock is occuring during a call to OTBind. The next step is to work out which type of endpoint ASP is trying to bind. Use MacsBug to set a "tvb" on OTBind. Also set a "tvb" on OTOpenEndpointPriv. You can then launch ASP and correlate the endpoints that get opened with the first parameter of OTBind (in R3 when the "tvb" fires). Once you know what type of endpoint is being bound, you can then try to figure out why it's deadlocking in your configuration.

S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware

References:
	>Re: Apple System Profiler & OT modules (From: Jean-Pierre <email@hidden>)

Prev by Date: Re: PBRemoteAccess function...
Next by Date: RE: PBRemoteAccess function...
Previous by thread: Re: Apple System Profiler & OT modules
Next by thread: Error -3212 ???
Index(es):
- Date
- Thread

Home