public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Rod Boyce <rod_boyce@DMCWave.com>
To: 'Keith Seitz' <keiths@cygnus.com>
Cc: "'insight@sourceware.cygnus.com'" <insight@sourceware.cygnus.com>
Subject: RE: Help getting insigh to work on cygwin.
Date: Tue, 28 Aug 2001 16:51:00 -0000	[thread overview]
Message-ID: <9DCCE20055ACD311BBE200104B08D8340127497C@EXCHWENZ01> (raw)

Keith,

Thank you for taking the time to answer my question.  As soon as you said
old version of cygwin.dll I remembered I did have an old version on my
system.  As soon as I deleted it all started working.

Regards,
Rod Boyce.

		-----Original Message-----
		From:	Keith Seitz [ mailto:keiths@cygnus.com ]
		Sent:	Wednesday, 29 August 2001 11:34
		To:	Rod Boyce
		Cc:	'insight@sourceware.cygnus.com'
		Subject:	Re: Help getting insigh to work on cygwin.

		On Wed, 29 Aug 2001, Rod Boyce wrote:

		> I get the following error message:
		>
		> $ powerpc-eabi-gdb.exe
		> d:\PPC\Bin\powerpc-eabi-gdb.exe: *** conflicting versions
of cygwin1.dll
		> detected.  Use only the most recent version.
		>
		>       0 [unknown (0xF8)] ? 0 lock_pinfo_for_update: rc 0,
pinfo_mutex
		> 0xFFFFFFFF, Win32 error 6
		>
		> Does anybody have any suggestions I need GDB5 with a nice
GUI and I have use
		> insight before?

		Somewhere insight has found a different cygwin1.dll from the
one your bash
		shell is using. What does "cygcheck -s -v -r -h" report?

		Use "find" to find all the cygwin1.dlls on your system. You
should only
		have one. See http://www.cygwin.com/faq for more
information.

		Keith

             reply	other threads:[~2001-08-28 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-28 16:51 Rod Boyce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-28 16:28 Rod Boyce
2001-08-28 16:34 ` Keith Seitz

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=9DCCE20055ACD311BBE200104B08D8340127497C@EXCHWENZ01 \
    --to=rod_boyce@dmcwave.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=keiths@cygnus.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).