<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Snipplr - gtcaz</title>
<link>http://snipplr.com/users/gtcaz/tags/cygwin</link>
<description>Recent snippets posted on Snipplr.com</description>
<language>en-us</language>
<pubDate>Wed, 22 May 2013 08:37:50 GMT</pubDate>
<item>
<title>(Other) Cygwin rxvt shortcut command</title>
<link>http://snipplr.com/view/2367/cygwin-rxvt-shortcut-command/</link>
<description><![CDATA[ <p></p> ]]></description>
<pubDate>Tue, 20 Mar 2007 12:29:18 GMT</pubDate>
<guid>http://snipplr.com/view/2367/cygwin-rxvt-shortcut-command/</guid>
</item>
<item>
<title>(Bash) Check cygwin apps for base conflicts</title>
<link>http://snipplr.com/view/2253/check-cygwin-apps-for-base-conflicts/</link>
<description><![CDATA[ <p>From: "Pierre A. Humblet" 
The attached script takes the name of a .exe or .dll,
uses cygcheck to find the dll dependence and checks for conflicts.

This will allow you to check your favorite applications or dlls,
seeing if --enable-auto-image-base works for you.

A "conflict" is when the end of a dll overlaps the start of the next one.
A "guard conflict" includes the extra 0x10000 mentioned by Jason in this thread.
They occur with Windows dlls, not sure if that's a real issue.

I have extended the tool (attached) so that it takes a variable number
of arguments. You can check a program and all the dll's it might ever
load dynamically, or all the dll's in /bin, or whatever. 
cygcheck will search the PATH if necessary.</p> ]]></description>
<pubDate>Thu, 08 Mar 2007 16:42:37 GMT</pubDate>
<guid>http://snipplr.com/view/2253/check-cygwin-apps-for-base-conflicts/</guid>
</item>
</channel>
</rss>