From: "Joe Smith" <unknown_kev_cat@hotmail.com>
To: cygwin@cygwin.com
Subject: Re: BitDefender again
Date: Sat, 29 Aug 2009 02:08:00 -0000 [thread overview]
Message-ID: <h7a2i3$qbj$1@ger.gmane.org> (raw)
In-Reply-To: <h73co7$tt1$1@ger.gmane.org>
"Michael Kairys" <kairys@comcast.net> wrote in message
news:h73co7$tt1$1@ger.gmane.org...
> Thanks for the replies...
>
>> the suggestion to use a base address in the 0x35000000 area (or indeed
>> any of the others they mentioned) is going to horribly frag your heap and
>> bork
>> your maximum allocatable memory limit, isn't it?
>
> I don't know. How would I tell?
>
>> Wonder if it wouldn't work just as well to rebase /their/ DLL?
>
> I don't know. Sounds scary given the liberties an AV program seems to take
> with the operating system... Should I try? How would I?
If you can figure out which DLL they are injecting, you can do exactly what
they tell you to do, except using their DLL instead of the cygwin DLL.
Or you can go the easy route, and follow the instructions they have provided
to rebase cygwin.dll. The person who wrote the message you quoted is
obviously familar with Cygwin, since he has you use Cygwin's rebase utility.
This indicates to me that he has actually tried the solution he mentions,
and it has fixed the problem for him.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2009-08-29 2:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 0:10 Michael Kairys
2009-08-26 1:36 ` Christopher Faylor
2009-08-26 11:37 ` Dave Korn
2009-08-26 13:19 ` Michael Kairys
2009-08-26 15:29 ` Wilfried
2009-08-27 13:19 ` Michael Kairys
2009-08-28 15:05 ` Wilfried
2009-08-29 2:08 ` Joe Smith [this message]
2009-09-01 13:28 ` Michael Kairys
2009-09-03 19:32 ` Michael Kairys
2009-09-10 12:04 ` Michael Kairys
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='h7a2i3$qbj$1@ger.gmane.org' \
--to=unknown_kev_cat@hotmail.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).