X-Spam-Check-By: sourceware.org Message-ID: <439B446C.F10D4F0C@dessent.net> Date: Sat, 10 Dec 2005 13:11:08 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.5.18-1: issue with cygwin1.dll: "system shared memory version mismatch detected" References: <20051210175558 DOT 2546 DOT qmail AT web86804 DOT mail DOT ukl DOT yahoo DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Igor Pechtchanski wrote: > Yes, you could try using ProcessExplorer or some other tools (e.g., > "handle") from SysInternals.com (ProcessExplorer can give you a list of > all loaded DLLs, for example). However, I don't think they will let you > search by the shared memory region name... You can in fact do this. Since Process Explorer shows all handles in use by the process, you can also see the handle to the shared memory region. The stock name is \BaseNamedObjects\cygwin1S4.shared.4. So you can use Procexp's "find handle" feature and search for "cygwin1S4.shared". Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/