cygwin bughunt (FAQ alert?)

Christopher Faylor cgf-no-personal-reply-please@cygwin.com
Fri Jan 21 21:54:00 GMT 2005


On Fri, Jan 21, 2005 at 02:26:39PM -0500, Igor Pechtchanski wrote:
>On Fri, 21 Jan 2005, Christopher Faylor wrote:
>
>> On Fri, Jan 21, 2005 at 11:53:25AM -0500, Igor Pechtchanski wrote:
>> >Also agreed.  But the source provided in the cygwin source package is
>> >worthless for debugging, since one can't build Cygwin from that source.
>> >If debugger symbols were available, that source would actually be
>> >useful.  :-)
>>
>> Huh?
>>
>>   tar xjf cygwin-1.5.12-1-src.tar.bz2
>>   cd cygwin-1.5.12-1
>>   mkdir build
>>   cd build
>>   (../configure; make) >& make.out
>>
>> This builds a cygwin DLL.  Just tried it.
>
>Whoops!  Apologies for providing outdated information...  At some point
>this required a CVS version of w32api, IIRC.
>
>For the archives, adding "--enable-debugging" to "../configure" above
>should build a debug version of the DLL.

I wouldn't suggest doing this unless you've been instructed to do so.
This adds extra debugging hooks into cygwin which provide more strace
output or pop up the debugger on certain types of situations.

The goal here is to build a version of the DLL which is the same as the
release.

The DLL that gets produced by the above has debugging symbols so this
is what is required.

cgf

--
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/



More information about the Cygwin mailing list