From: "Akula, Murali" <makula@qualcomm.com>
To: <cygwin@cygwin.com>
Subject: RE: system shared memory mismatch problem
Date: Thu, 03 Jul 2008 00:40:00 -0000 [thread overview]
Message-ID: <CFF00D6467131149AF5437F4663580D801C94F55@NAEX15.na.qualcomm.com> (raw)
In-Reply-To: <486C1F28.6090200@cygwin.com>
>On 07/02/2008, Akula, Murali wrote:
>> I tried searching with 'Search Hiden Files & Folders' checked. It
still
>> shows only one cygwin1.dll
>
> Then try "Process Explorer". Grab it from sysinternals.com. With
that,
> you can find out what process is running cygwin1.dll and where it is.
Great tool!! Thanks. Tried it. I ran rxvt from the new cygwin
installation and that's what's showing up (and sh) as using the
cygwin1.dll. The one from c:\cygwin\bin is being used by these apps.
If I exit rxvt, then there's no other process using the cygwin1.dll.
Looks like there is no other version of cygwin1.dll running. Do I have
something really corrupted.
I was actually wondering how can I run rxvt and some other tools, while
I cannot run X, etc.. Do they use shared memory differently? Or not
make the version checks?
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
--
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/
next prev parent reply other threads:[~2008-07-03 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 0:08 Akula, Murali
2008-07-03 0:22 ` Larry Hall (Cygwin)
2008-07-03 0:40 ` Akula, Murali [this message]
2008-07-03 0:46 ` Christopher Faylor
2008-07-03 1:38 ` Akula, Murali
2008-07-03 3:26 ` Larry Hall (Cygwin)
-- strict thread matches above, loose matches on Subject: below --
2008-07-02 21:02 Akula, Murali
2008-07-02 22:11 ` Larry Hall (Cygwin)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CFF00D6467131149AF5437F4663580D801C94F55@NAEX15.na.qualcomm.com \
--to=makula@qualcomm.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).