Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!veritas!amdcad!sun!plx!evan From: evan@plxsun.uucp (Evan Bigall) Newsgroups: comp.databases Subject: Re: How would YOU solve this problem??? Message-ID: Date: 27 Mar 91 00:34:32 GMT References: <21464@shlump.nac.dec.com> Sender: usenet@plx.UUCP Distribution: usa Organization: Plexus Software Inc. Lines: 20 In-reply-to: r_anderson@quickr.enet.dec.com's message of 26 Mar 91 18:38:35 GMT In article <21464@shlump.nac.dec.com> r_anderson@quickr.enet.dec.com (Rick Anderson) writes: [Big problem deleted] Here's the question: How would you go about determining what process is corrupting the shared memory addresses? I'd stay up late a few nights doing whatever your preferred activity for softening the brain is (the deities in charge expect penance) and then smack yourself in forehead and yell "ahhhhhh Ha!!!" This may not be the response you were looking for, but I have solved this sort of problem before, and thats how I always did it. /Evan PS: you may want to mention the software involved, and the accessibility of code/tools. -- Evan Bigall, Plexus Software, Santa Clara CA (408)982-4840 ...!sun!plx!evan "I barely have the authority to speak for myself, certainly not anybody else"