Re: Fork issue on W10 WOW
Am 14.07.2018 um 21:03 schrieb Brian Inglis: On 2018-07-14 11:58, Achim Gratz wrote: Marco Atzeri writes: Anyway, the only time I've seen similar behaviour was when some other library was occupying the address space the systems libraries should have occupied, and the they get some extremely random address assigned until the next reboot. To do this the other library must however be loaded pretty early in the boot process. If you wrote the mail on said laptop, this Diese E-Mail wurde von AVG auf Viren geprüft. might be an explanation for the whole thing. AVG is well known for intercepting things already during boot and loading a bunch of their libraries early. Some of it is still done even if you switch it off completely and some changes to the registry might even survive a deinstallation. +1 for AVG BLODA - had to deinstall that years ago, and was slow; only reason I still run an AV is to catch stuff, either in Windows binaries from download sources about which little info is publicly available, or in email which folks I trust forward once in a blue moon, from their greedy or gullible infected friends, who are in the main, clueless or in denial about it. In this case AVG is innocent. I removed all AV and the lottery is still there 63DF-63DF1000 74F4-74F41000 5DE2-5DE21000 it seems the WOW64*.dll can be anywhere between 5000-7F00 The 32 applications present at boot are: HP Cool Sense HP Audio Switch HP Jump Start HP Message Service Microsoft OneDrive Lavasof Webcompanion Wordweb Dictionary and also Lavasoft seems innocent as after removal 5C90-5C901000 5EE7-5EE71000 I will wait until 1803 is installed, download is in progress, before making new trials/experiments Regards Marco -- 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
Re: How to Setup Multiple System Distro Manpages
On 7/14/2018 10:50 PM, Brian Inglis wrote: Hi folks, I've installed a few WSL distros for comparison and downloaded a bunch of other manpage sets and unpacked them: $ l src/man/*[0-9].tar.gz src/man/CentOS_7.1.tar.gz src/man/NetBSD_7.1.tar.gz src/man/Darwin_7.0.1.tar.gzsrc/man/OpenBSD_6.2.tar.gz src/man/Debian_8.1.0.tar.gzsrc/man/Red_Hat_Linux_i386_9.tar.gz src/man/FreeBSD_12.tar.gz src/man/SunOS_5.10.tar.gz src/man/FreeBSD_Ports_11.1.tar.gz src/man/SuSE_Linux_i386_11.3.tar.gz src/man/HP-UX_11.22.tar.gz src/man/X11_R7.4.tar.gz $ l /proc/cygdrive/c/usr/local/share/man/ cat1/ debian@ man1p/ mann/ SunOS-5.10/ cat3/ Debian-8.1.0/man2/ netbsd@ suse@ cat5/ freebsd@ man3/ NetBSD-7.1/ SuSE-11.3/ cat7/ FreeBSD-12-current/ man3p/ openbsd@ubuntu@ cat8/ FreeBSD-ports-11.1-RELEASE/ man4/ OpenBSD-6.2/x@ centos@hpux@man5/ ports@ X11R7.4/ CentOS-7.1/HP-UX-11.22/ man6/ redhat@ darwin@man0p/ man7/ RedHat-9-i386/ Darwin-7.0.1/ man1/man8/ solaris@ but despite reading docs, adding links and changing configs, I'm unable to get man/-db to access these with or without the -m system switch. I know I must be missing some essential point, but searching has not come up with anything to help me fix this. Has anyone here set this up and can suggest an approach that will work? In addition to the other answers; maybe exporting those directories in the 'PATH' env variable... -- John Doe -- 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
Re: How to Setup Multiple System Distro Manpages
On 07/14/2018 04:50 PM, Brian Inglis wrote: I've installed a few WSL distros for comparison and downloaded a bunch of other manpage sets and unpacked them: $ l /proc/cygdrive/c/usr/local/share/man/ cat1/ debian@ man1p/ mann/ SunOS-5.10/ cat3/ Debian-8.1.0/ man2/ netbsd@ suse@ cat5/ freebsd@ man3/ NetBSD-7.1/ SuSE-11.3/ cat7/ FreeBSD-12-current/ man3p/ openbsd@ ubuntu@ cat8/ FreeBSD-ports-11.1-RELEASE/ man4/ OpenBSD-6.2/ x@ centos@ hpux@ man5/ ports@ X11R7.4/ CentOS-7.1/ HP-UX-11.22/ man6/ redhat@ darwin@ man0p/ man7/ RedHat-9-i386/ Darwin-7.0.1/ man1/ man8/ solaris@ but despite reading docs, adding links and changing configs, I'm unable to get man/-db to access these with or without the -m system switch. I know I must be missing some essential point, but searching has not come up with anything to help me fix this. Has anyone here set this up and can suggest an approach that will work? Works fine for me, in the usual place however, not using /usr/local: /usr/share/man/alt/man1/foo.1 man -m alt foo -- 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
Re: How to Setup Multiple System Distro Manpages
On Sat, Jul 14, 2018 at 1:51 PM Brian Inglis wrote: > $ l /proc/cygdrive/c/usr/local/share/man/ Shouldn't those be under /usr/local instead of /proc/cygdrive/c/usr/local? Typically /usr is something like C:/cygwin64/usr, which is not the C:/usr dir you've used. ..wayne.. -- 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
Re: How to Setup Multiple System Distro Manpages
On 2018-07-14 16:40, Jack wrote: > On 07/14/2018 04:50 PM, Brian Inglis wrote: >> I've installed a few WSL distros for comparison and downloaded a bunch of >> other >> manpage sets and unpacked them: >> $ l /proc/cygdrive/c/usr/local/share/man/ >> cat1/ debian@ man1p/ mann/ >> SunOS-5.10/ >> cat3/ Debian-8.1.0/ man2/ netbsd@ suse@ >> cat5/ freebsd@ man3/ NetBSD-7.1/ >> SuSE-11.3/ >> cat7/ FreeBSD-12-current/ man3p/ openbsd@ ubuntu@ >> cat8/ FreeBSD-ports-11.1-RELEASE/ man4/ OpenBSD-6.2/ x@ >> centos@ hpux@ man5/ ports@ X11R7.4/ >> CentOS-7.1/ HP-UX-11.22/ man6/ redhat@ >> darwin@ man0p/ man7/ RedHat-9-i386/ >> Darwin-7.0.1/ man1/ man8/ solaris@ >> >> but despite reading docs, adding links and changing configs, I'm unable to >> get >> man/-db to access these with or without the -m system switch. >> >> I know I must be missing some essential point, but searching has not come up >> with anything to help me fix this. >> >> Has anyone here set this up and can suggest an approach that will work? >> > Purely a guess on my part, but should those directories all start with "man" > (or > "cat") ? >From docs I have checked, man is the default name for the current system e.g. man -m man, and freebsd, debian, etc. should be at the same level, with man?, cat?, xx_XX, directories below that, so I have linked and moved them up and down the hierarchy, modified /etc/man_db.conf to match, rerun mandb, and tried using "man -m freebsd ...", etc. without any success as far as I can tell. I have other system man and cat directories in my MANPATH at various levels above and under Cygwin, and can access those manpages, just not the alternative systems. I am sure I must have missed something unobvious in the docs, and noticed nothing about this in the books, which I have checked. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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
Re: How to Setup Multiple System Distro Manpages
On 07/14/2018 04:50 PM, Brian Inglis wrote: Hi folks, I've installed a few WSL distros for comparison and downloaded a bunch of other manpage sets and unpacked them: $ l src/man/*[0-9].tar.gz src/man/CentOS_7.1.tar.gz src/man/NetBSD_7.1.tar.gz src/man/Darwin_7.0.1.tar.gzsrc/man/OpenBSD_6.2.tar.gz src/man/Debian_8.1.0.tar.gzsrc/man/Red_Hat_Linux_i386_9.tar.gz src/man/FreeBSD_12.tar.gz src/man/SunOS_5.10.tar.gz src/man/FreeBSD_Ports_11.1.tar.gz src/man/SuSE_Linux_i386_11.3.tar.gz src/man/HP-UX_11.22.tar.gz src/man/X11_R7.4.tar.gz $ l /proc/cygdrive/c/usr/local/share/man/ cat1/ debian@ man1p/ mann/ SunOS-5.10/ cat3/ Debian-8.1.0/man2/ netbsd@ suse@ cat5/ freebsd@ man3/ NetBSD-7.1/ SuSE-11.3/ cat7/ FreeBSD-12-current/ man3p/ openbsd@ubuntu@ cat8/ FreeBSD-ports-11.1-RELEASE/ man4/ OpenBSD-6.2/x@ centos@hpux@man5/ ports@ X11R7.4/ CentOS-7.1/HP-UX-11.22/ man6/ redhat@ darwin@man0p/ man7/ RedHat-9-i386/ Darwin-7.0.1/ man1/man8/ solaris@ but despite reading docs, adding links and changing configs, I'm unable to get man/-db to access these with or without the -m system switch. I know I must be missing some essential point, but searching has not come up with anything to help me fix this. Has anyone here set this up and can suggest an approach that will work? Purely a guess on my part, but should those directories all start with "man" (or "cat") ? Jack -- 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
How to Setup Multiple System Distro Manpages
Hi folks, I've installed a few WSL distros for comparison and downloaded a bunch of other manpage sets and unpacked them: $ l src/man/*[0-9].tar.gz src/man/CentOS_7.1.tar.gz src/man/NetBSD_7.1.tar.gz src/man/Darwin_7.0.1.tar.gzsrc/man/OpenBSD_6.2.tar.gz src/man/Debian_8.1.0.tar.gzsrc/man/Red_Hat_Linux_i386_9.tar.gz src/man/FreeBSD_12.tar.gz src/man/SunOS_5.10.tar.gz src/man/FreeBSD_Ports_11.1.tar.gz src/man/SuSE_Linux_i386_11.3.tar.gz src/man/HP-UX_11.22.tar.gz src/man/X11_R7.4.tar.gz $ l /proc/cygdrive/c/usr/local/share/man/ cat1/ debian@ man1p/ mann/ SunOS-5.10/ cat3/ Debian-8.1.0/man2/ netbsd@ suse@ cat5/ freebsd@ man3/ NetBSD-7.1/ SuSE-11.3/ cat7/ FreeBSD-12-current/ man3p/ openbsd@ubuntu@ cat8/ FreeBSD-ports-11.1-RELEASE/ man4/ OpenBSD-6.2/x@ centos@hpux@man5/ ports@ X11R7.4/ CentOS-7.1/HP-UX-11.22/ man6/ redhat@ darwin@man0p/ man7/ RedHat-9-i386/ Darwin-7.0.1/ man1/man8/ solaris@ but despite reading docs, adding links and changing configs, I'm unable to get man/-db to access these with or without the -m system switch. I know I must be missing some essential point, but searching has not come up with anything to help me fix this. Has anyone here set this up and can suggest an approach that will work? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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
Re: Fork issue on W10 WOW
On 2018-07-14 11:58, Achim Gratz wrote: > Marco Atzeri writes: > Anyway, the only time I've seen similar behaviour was when some other > library was occupying the address space the systems libraries should > have occupied, and the they get some extremely random address assigned > until the next reboot. To do this the other library must however be > loaded pretty early in the boot process. If you wrote the mail on said > laptop, this >> Diese E-Mail wurde von AVG auf Viren geprüft. > might be an explanation for the whole thing. AVG is well known for > intercepting things already during boot and loading a bunch of their > libraries early. Some of it is still done even if you switch it off > completely and some changes to the registry might even survive a > deinstallation. +1 for AVG BLODA - had to deinstall that years ago, and was slow; only reason I still run an AV is to catch stuff, either in Windows binaries from download sources about which little info is publicly available, or in email which folks I trust forward once in a blue moon, from their greedy or gullible infected friends, who are in the main, clueless or in denial about it. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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
Re: Fork issue on W10 WOW
Marco Atzeri writes: > Nothing fancy, just vanilla fresh new > W10 64bit Home preinstalled on HP Notebook > German Language > Version 1709 > Build system 16299.547 Hmmm. That should update itself to 1803 almost the same second you let it anywhere near a network. Anyway, the only time I've seen similar behaviour was when some other library was occupying the address space the systems libraries should have occupied, and the they get some extremely random address assigned until the next reboot. To do this the other library must however be loaded pretty early in the boot process. If you wrote the mail on said laptop, this > Diese E-Mail wurde von AVG auf Viren geprüft. might be an explanation for the whole thing. AVG is well known for intercepting things already during boot and loading a bunch of their libraries early. Some of it is still done even if you switch it off completely and some changes to the registry might even survive a deinstallation. It sounds like you've already spent way more time with that problem than you thought you would, but my suggestion is to try a clean boot of a stock Windows installation. You can install one into a VHD and (multi-)boot into it without affecting your existing installation beyond the space taken up by the VHD file (german magazine c't has described both a manual way of doing that and developed a script that prepares the VHD so that it just needs to complete the installation when first booted). If that works OK without your current problems, you can then decide whether to keep a separate boot environment, trying to fix your existing install or wiping the pre-installed Windows and doing a fresh install on bare iron. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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
[ANNOUNCEMENT] meson 0.47.1-1
The following packages have been uploaded to the Cygwin distribution: * meson-0.47.1-1 Meson is an open source build system meant to be extremely fast. It generates files for various backends including Ninja, Visual Studio, and Xcode. Meson does not generate Makefiles, relying solely on Ninja for Linux and Unix support. This is an update to the latest upstream release: http://mesonbuild.com/Release-notes-for-0-47-0.html noarch: 5bf2912504b855e84d7a9570642ea5de293b04c8e6c7ef9fe7f04e5029d66614058e2a47d6045ab6326c33d2c1bfed1d760c17058eb6061fd09d228d090e6562 *meson-0.47.1-1-src.tar.xz 7f3aee107461f417ddf02373c7928c1d49cbe324d2b5110e25f0b32c81566557295d503ab7e11e01e40f8970541c03f5f84a8048f6e7ef9a3059b386e6f67cd5 *meson-0.47.1-1.tar.xz -- 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
Re: Fork issue on W10 WOW
Am 14.07.2018 um 16:50 schrieb Achim Gratz: Marco Atzeri writes: currently I have over 7300 always busy 73C5-73C51000 /cygdrive/c/Windows/SysWOW64/cryptbase.dll What type of Windows do you use? I have Home N for testing at home and Server 2016 plus a bunch of users w/ Enterprise clients (will get one myself in a few days) and never seen any such problems. .. Are you using one of the preview update channels or did you use one in the past? Leading up to 1803 MS has apparently tested some new ASLR tricks and I don't think they change the settings back to default even when you are later switching back to a "normal" release version. Anyway, with 1803 there is a setting now in the security panel somewhere that forces ASLR to be used even when the PE flags say otherwise. I don't know if that can be switched on just for the WoW64 subsystem, but it would probably be something you can do via group policy (on a Pro or Enterprise client). Nothing fancy, just vanilla fresh new W10 64bit Home preinstalled on HP Notebook German Language Version 1709 Build system 16299.547 Regards, Achim. Regards Marco --- Diese E-Mail wurde von AVG auf Viren geprüft. http://www.avg.com -- 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
Re: Fork issue on W10 WOW
Marco Atzeri writes: > currently I have over 7300 always busy > 73C5-73C51000 /cygdrive/c/Windows/SysWOW64/cryptbase.dll What type of Windows do you use? I have Home N for testing at home and Server 2016 plus a bunch of users w/ Enterprise clients (will get one myself in a few days) and never seen any such problems. >> You could reboot the machine until the DLLs are at an adddress you >> can work with and then never reboot again. /duck/ > > Feasible, just time consuming.. > It took a dozen trials before reaching a nice > > 71D1-71D11000 /cygdrive/c/Windows/System32/wow64.dll > > the last lottery numbers were: > > 5A9B-5A9B1000 > 66AB-66AB1000 > 53DA-53DA1000 > 6A47-6A471000 > 6DBF-6DBF1000 > 5F02-5F021000 > 680D-680D1000 > 5265-52651000 > 71D1-71D11000 > > Now I am stuck to German system and never > restart. Until next MS patch day... Are you using one of the preview update channels or did you use one in the past? Leading up to 1803 MS has apparently tested some new ASLR tricks and I don't think they change the settings back to default even when you are later switching back to a "normal" release version. Anyway, with 1803 there is a setting now in the security panel somewhere that forces ASLR to be used even when the PE flags say otherwise. I don't know if that can be switched on just for the WoW64 subsystem, but it would probably be something you can do via group policy (on a Pro or Enterprise client). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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
Re: Win32::GUI Installation
Badoobj Badoobj writes: > I am trying to install Win32-GUI 1.06. The version I downloaded does not > have an executable. The current version of this package for Cygwin is 1.14 and 1.06 is so old that it should be no longer available on anyof the mirrors. > I just want to verify if it does not require an > executable to be ran. It's a Perl module, so it will require some Perl script to be run by Perl if you want to use it. > I am new to using the application. Please assist. Again it's not an application. I have no idea what you're trying to achieve, so further assistance can not be given. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- 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
Re: running self compiled 32 bit binary on 64 bit Windows?
Ulli Horlacher writes: >> You have to install Cygwin, not "transfer". > > I have several 100 users, none of them is able to install cygwin and > the packages they need the official way, they are way to *CENSORED* for > this job :-} If they can follow your current instructions, they can surely start some script that does this correctly? > I give them my preconfigured cygwin.zip (or cygwin64.zip) and tell them to > unpack it in C:\ > > http://fex.belwue.de/usecases/cygwin.html > > (This is what I call "transfer cygwin") Whatever you call it, it's still cludgey nonsense that might or might not work. Only when it's not working your users will really be unable to figure out what to do since they won't even know what is failing. Again, to provide your tools properly for Cygwin, create a Cygwin package, set up a package repository that provides it and then start a script that calls setup to install it and any other packages you need (if not already installed by way of dependency). Setup can deal with multiple package repositories, so you can use one of the official mirrors as the primary package repository and only provide your package as an add-on repository (like cygwin ports does). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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
[ANNOUNCEMENT] gdb-8.0.1-1 (TEST)
The following package has been updated in the Cygwin distribution: * gdb-8.0.1-1 The GNU debugger allows you to debug programs written in C, C++, and other languages, by executing them in a controlled fashion and printing their data. This is an update to a later upstream version: https://sourceware.org/ml/gdb-announce/2017/msg4.html See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes. In addition, it contains the following patches carried forward from the previous Cygwin package: * Teach the demangler to deal with '@'-decorated __stdcall functions * Various fixes for Cygwin signal handling * (experimental) Teach gdb how to unwind frames for the Cygwin signal delivery wrapper functions _sigbe and sigdelayed * Warn rather than stopping with an error if realpath() for a DLL fails (Tim Chick) Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00401.html * Fix a memory leak which would occur in the case when the result of realpath() is greater than or equal to SO_NAME_MAX_PATH_SIZE (Corinna Vinschen) * Fix inferior stopping with SIGTTIN, if it tries to read from the terminal after it has been continued Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00285.html * Workaround https://sourceware.org/bugzilla/show_bug.cgi?id=21078 by linking with shared libstc++ and libgcc. Addresses: https://cygwin.com/ml/cygwin/2017-10/msg00109.html x86: 7975309cd6f9f1f7e5fb109d3b1511aa749bc3aa3816a9ecc9ee2f57792c9e637b878e36f5485fd639e422d1145a91ecb836337a4884b2259c279da1d865db1d *gdb-8.0.1-1-src.tar.xz af6eec52bb7194c59127391564e7330dfd322b442e53b28492b95285139698294a7b317115942a78831d0cb54e802310d2cbcc06df674f61f659d6b2fe27e924 *gdb-8.0.1-1.tar.xz 6477438617a400e22467754acd0c01fd8c8852af0e3cd38f1da82a26306a6a57d92051aa2b15be5b05f52ee8db6430bf8c69da2e66d534dfb3275b9a9827d5f0 *gdb-debuginfo-8.0.1-1.tar.xz x86_64: b88c08572cad31a6f6807be532319461af18a69a79491f93809854a7d5113871e6c7880e65193d572515cd61a837157c35641a61cf90d5a92a655f99d31849ca *gdb-8.0.1-1-src.tar.xz a6543fff99a16816dfa8bab7884256f7cfef810303edf3cc27111e9e1379641d72f61d97099d886f44277d1445871f71a7f93635e71855e88c6d43e39ec27446 *gdb-8.0.1-1.tar.xz 3a6847dbb86e3d50a033e2ceb1d08ed9978a39ba1516fb18423e05630cde07d36236987fc96be06a9783decc112cb6c3565f865b85491cd0189b214a7e8a44c3 *gdb-debuginfo-8.0.1-1.tar.xz -- 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
