Right you are, David.  I was assuming that the name coming in to
_dxf_ExCacheStrPrepend began with / and ended with :, based evidence
aquired in a little test script.  Turns out that the topmost macro isn't
considered an instance, so doesn't have the / or the :.  Just in case my
assumption was wrong I put in a check for the lack of these and put out a
message, but didn't take the one small extra step of handling the case.

Looks like this sample didn't work (but didn't coredump) prior to Fridays
fix.

Greg.

"David L. Thompson" <[EMAIL PROTECTED]>@opendx.watson.ibm.com on
08/28/2000 12:24:07 AM

Please respond to [email protected]

Sent by:  [EMAIL PROTECTED]


To:   [email protected]
cc:
Subject:  [opendx-dev] Problem in graph.c with ArrangeMember



Greg, Randall,

With the latest updates on the cache graph stuff, there is a problem
with the ArrangeMember macro. With the SuperviseState and
SuperviseWindow in the macro, a core dump occurs. I've traced it to
the new function Greg built, but it looks like it is a problem with
the Async modules being in a macro. As the function is called
recursively, it seems to have problems. Any clue as to the easy fix?
If not, I will start digging into the gory details.

David
--
.............................................................................

David L. Thompson                          The University of Montana
mailto:[EMAIL PROTECTED]                 Computer Science Department
http://www.cs.umt.edu/u/dthompsn           Missoula, MT  59812
                                            Work Phone : (406)257-8530


Reply via email to