Re: gdb received signal SIGSEGV before even entering main!
At 01:03 AM 12/1/2002, Christopher Faylor wrote: >On Sat, Nov 30, 2002 at 11:55:18PM -0500, Larry Hall (RFK Partners, Inc) wrote: > > > >At 12:55 AM 11/29/2002, [EMAIL PROTECTED] wrote: > >>The program I ran gdb on a very standard hello world program, it > >>crashes even before main is entered. Anybody have an idea how to solve > >>this problem? Any help is appreciated. > > > >I think you'll find some help for this in the email archives. For > >details, do a quick search and see the previous discussions. If you're > >less interested in the details, just type "cont" and continue running > >gdb. In the future, it's worthwhile for you to check the email > >archives prior to posting, in case the issue you have has been > >discussed previously. > >FWIW, I think this problem was fixed in 1.3.16. So, if this is a problem >it probably is due to an older version of cygwin. Good news! :-) Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gdb received signal SIGSEGV before even entering main!
On Sat, Nov 30, 2002 at 11:55:18PM -0500, Larry Hall (RFK Partners, Inc) wrote: > >At 12:55 AM 11/29/2002, [EMAIL PROTECTED] wrote: >>The program I ran gdb on a very standard hello world program, it >>crashes even before main is entered. Anybody have an idea how to solve >>this problem? Any help is appreciated. > >I think you'll find some help for this in the email archives. For >details, do a quick search and see the previous discussions. If you're >less interested in the details, just type "cont" and continue running >gdb. In the future, it's worthwhile for you to check the email >archives prior to posting, in case the issue you have has been >discussed previously. FWIW, I think this problem was fixed in 1.3.16. So, if this is a problem it probably is due to an older version of cygwin. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Question/bug? : Make and tab problem since version 1.3.16...
2 fixes to the line, it should be: sometarget: $(shell echo -e '$(VAR1)' >> $@) this $(shell... makes a file called "somefile", in it you will see: " a.o:a.c cc $@ " I'm including this sometarget in the makefile thus extending it "on the fly", believe me it works ! -Original Message- From: Max Bowsher [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 7:38 PM To: Moti Daniel; [EMAIL PROTECTED] Subject: Re: Question/bug? : Make and tab problem since version 1.3.16... Moti Daniel <[EMAIL PROTECTED]> wrote: > After upgrading cygwin dll to 1.3.16 from 1.3.12 I had the following > problem: > I'm using cygwin to build my project, in my makefile I'm creating > another makefile like this: > VAR1=a.o : a.c\n\tcc $$@ > . > . > . > sometarget : > $(shell echo -e '$(VAR1)' >> somefile > > before the upgrade this produced somefile with this lines in it: > a.o : a.c > cc $@ I find that hard to believe. With that $(shell... in there, make tries to run a program 'a.o'. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: gdb received signal SIGSEGV before even entering main!
At 12:55 AM 11/29/2002, [EMAIL PROTECTED] wrote: >The program I ran gdb on a very standard hello world program, it crashes even >before main is entered. >Anybody have an idea how to solve this problem? >Any help is appreciated. I think you'll find some help for this in the email archives. For details, do a quick search and see the previous discussions. If you're less interested in the details, just type "cont" and continue running gdb. In the future, it's worthwhile for you to check the email archives prior to posting, in case the issue you have has been discussed previously. Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: bash isn't running my .bashrc!
At 09:44 AM 11/28/2002, Chris Game wrote: >The login shell stuff sent me to look at the etc/passwd file and the >stuff about that in the cygwin FAQ. As an occasional user of cygwin I >have to say I find these documents written at too high a level to take >in easily. A couple of hours searching for and reading and understanding >docs is way too much for occasional users. Understood. Would you like to offer some suggestions/additions for the documentation with a patch? Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug report: ls reports a HUGE file size for a file over 2 Gb
On Sat, Nov 30, 2002 at 03:22:42PM -0500, David Edwards wrote: >"ls" reports a 2.6Gb file as being huge! This is under an XP Pro, NTFS >partition with cygwin, 1.3.17-1 using ls from fileutils, 4.1-1. The >following shows the incorrect size for fred3.zero from "ls" and the correct >size from a similar dir command. Cygwin does not support files greater than 2GB. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Bug report: ls reports a HUGE file size for a file over 2 Gb
"ls" reports a 2.6Gb file as being huge! This is under an XP Pro, NTFS partition with cygwin, 1.3.17-1 using ls from fileutils, 4.1-1. The following shows the incorrect size for fred3.zero from "ls" and the correct size from a similar dir command. The file was created with: dd if=/dev/zero of=fred3.zero bs=4096 count=655370 *** Cygwin bash shell *** edwards@MONTESA ~ $ ls -l *.z* -rw-rw-rw-1 edwards None12288 Nov 30 10:57 fred1.zero -rw-rw-rw-1 edwards None 1610612736 Nov 30 11:05 fred2.zero -rw-rw-rw-1 edwards None 18446744072098979840 Nov 30 11:14 fred3.zero edwards@MONTESA ~ $ ls -hl *.z* -rw-rw-rw-1 edwards None 12k Nov 30 10:57 fred1.zero -rw-rw-rw-1 edwards None 1.5G Nov 30 11:05 fred2.zero -rw-rw-rw-1 edwards None 16E Nov 30 11:14 fred3.zero *** DOS Command Prompt *** C:\cygwin\home\edwards>dir *z* Volume in drive C has no label. Volume Serial Number is C4C0-5C1C Directory of C:\cygwin\home\edwards 10/19/2002 06:05 PM 477 .zip 11/30/2002 10:57 AM12,288 fred1.zero 11/30/2002 11:05 AM 1,610,612,736 fred2.zero 11/30/2002 11:14 AM 2,684,395,520 fred3.zero 4 File(s) 4,295,021,021 bytes 0 Dir(s) 6,434,316,288 bytes free Thanks David Edwards --- Begin Message --- --- End Message --- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
FAQ now misleads about cygcheck output
For the Cygwin FAQ maintainer: Quoted from the FAQ under "Posting Guidelines" -- Details about your Cygwin setup, accomplished by pasting the output of 'cygcheck -s -v -r' into your message. (Do not send the output as a file attachment.) Recent discussion suggests the advice is now obsolete. It may also be an idea to state that the now-desirable attachment should not be compressed. FYI Jason C. Johnston <[EMAIL PROTECTED]> -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: winpids::enumNT: error 0xC0000005 - huh?
Chris, This has apparently been fixed in 1.3.17 - I updated my dual-processor machine, and have not seen that error message the entire evening. R. Christopher Faylor wrote: On Sun, Nov 24, 2002 at 04:10:56PM +, Rui Carmo wrote: Having suffered from repeated rxvt hangs, I dutifully downloaded the latest Cygwin DLL update, rebooted and resumed working on one of my pet projects: a barbaric hack of the netatalk packages to try and get an AppleShare IP file service running under cygwin. Almost immediatly, however, I began getting messages like this: 11 [sig] bash 2808 winpids::enumNT: error 0xC005 reading system process information ...when running configure/shell/Perl scripts. I copied my build tree across to another box (with the older Cygwin version) and re-ran the relevant scripts - without any of these error messages. I'm pretty sure this is related to the new version, since it was the only change on my main box (I had upgraded everything a couple of days or on all boxes). Any ideas? Yep, and they are all in http://cygwin.com/bugs.html cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: [Patch] skipping import libraries for performance reasons - direct auto-import of dll's
> > The only thing I like to say is, that instead of using a symbolic > link to the > > dll, the "unix" way may be possible. > > What I mean is to put the dll into the lib dir (like the .so > libraries in unix, > > the bin dir contains only executables) and to implement a LD_LIBRARY_PATH > > environmen support into cygwin1.dll, so that the dll could be used > directly. But > > this is only an idea and there may be objectivies not to do so. > > No, not really. The windows runtime loader handles loading the DLL, and > IT doesn't understand "LD_LIBRARY_PATH" and never will (closed source, > MS, yadda yadda). So it doesn't really matter whether cygwin1.dll > understands LD_LIBRARY_PATH or not -- cygwin1.dll is not involved in > loading DLLs (except for dlopen(), but that's a different subject). > > Two choices: >1) put /usr/lib, /usr/local/lib, etc etc into $PATH >2) or do the symlink thing > > Personally, I don't want to clutter the PATH with a bunch of lib > directories -- and neither do you, Ralf. You're always worried about > speed on cygwin, and proposing things like auto-rebasing and prelinking > and all sorts of disruptive things. > > But according to MSDN, the one thing that slows program startup the MOST > is searching for DLLs in a long PATH. So, keep PATH short -- which > means the DLLs need to live in the 'bin' directories which are already > in the PATH. That means > > we either put -L/usr/bin and suchlike into the gcc specs file (BLECH!) > or do the symlink thing. Me, I vote for symlinks. :-) > Chuck, thanks for answering. Yes you're right. symlinking seems to me as the best way. BTW: I'm astonished about your detailed and accurate writing. I wished, I could write a litter faster: -) Ralf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin official logo ?
On Fri, 29 Nov 2002, Charles Wilson wrote: > > Please grant me this one conceit. Linus likes penguins. I like > > otters. > > Me too. > > > If there is going to be an animal mascot for cygwin it should be an > > otter. > > Figured those FurryMuck people might be able to help -- they like to > draw cartoon animals. How about contacting this guy: > > http://www.tigress.com/lutra/art/images/bw/ltoyster.gif > http://www.tigress.com/lutra/english/commissions.htm > > This guy's "furry" persona (not sure of the terminology of this > subculture) is an otter, so most of his art is otter-ish. The "furry" subculture has been around for many years. I remember seeing people dressed in various half-man half-other at TimeCon(tm) back in the mid 70s. Furry can best described as a mutation between human and anything else. I recall it first started with animals which had fur (tigers, lions, cats, etc), hence the name "furry", but later branched out to other types of animals (sometime even alien). Many people choose an animal that they best identify with and create a persona based on that animal. There are even conventions devoted to Furry Folk (ConFURance is a popular one). Anyway, since he is an artist (and his work seems pretty good) and he does otters, it might be worth a few bucks to have him create something for Cygwin. [snip] > Otter info (for the truly obsessed; e.g. cgf ). Ya know, it's > really scary the sort of stuff that fills your bookshelf/bookmarks when > you're an engineer (e.g. detail oriented and trivia obsessed) and many > of your friends, coworkers, and their spouses are biologists, animal > behaviorists, or medical types. Sometimes I scare me. > > Or maybe it's just that I was reading "Ranger Rick" magazine and > collecting World Wildlife Fund "Animal Cards" when my kindergarten > playmates were into "Highlights". > > I still scare me. And you scare us too, Charles (just kidding :) [interesting classification information deleted] > --Chuck -- Peter A. Castro <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]> "Cats are just autistic Dogs" -- Dr. Tony Attwood -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin's autoconf?
Lapo Luchini wrote: I believe that autoreconf isn't entirely reliable. This is the reason that projects (e.g. libgetopt++) often have a bootstrap.sh which runs the relevant autotools. Doing "aclocal && automake && autoconf" as the autobook suggests doesn't change things... =( (or: it does seldom work, but usually doesn't.. that's why I'm thinking about granularity in NT's timekeeping) automake 1.7.x and later require autoconf-2.54 or newer. Ordinarily, the wrapper scripts in the cygwin autotools suite ensure that "matching" versions are called -- unless your installation is not fully uptodate. Make sure you have both autoconf-devel-2.54-... automake-1.7.1- installed, and check to see if your configure.[in|ac] file has an 'AC_PREREQ(x.xx)' line in it. --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin's autoconf?
I believe that autoreconf isn't entirely reliable. This is the reason that projects (e.g. libgetopt++) often have a bootstrap.sh which runs the relevant autotools. Doing "aclocal && automake && autoconf" as the autobook suggests doesn't change things... =( (or: it does seldom work, but usually doesn't.. that's why I'm thinking about granularity in NT's timekeeping) -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Requesting Help with malloc debugging.
I'm trying to debug a segfault from h8300-hms-ld. Can anyone give me any pointers on malloc debugging under Cygwin? Thanks. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin's autoconf?
Lapo Luchini <[EMAIL PROTECTED]> wrote: > Hi! > Finally I decided to study seriously the autotools (thanks for the > references, Nicholas!).. but I have a small problem: > > (cyberone is my CygWin/WinXP desktop machine, cyberx is my FreeBSD > home-server machine) > cyberone$ autoreconf > cyberone$ rsync -vrLe ssh --delete * lapo@cyberx:project/ > cyberx$ ./configure > [normal configure output] > cyberx$ make > cd . && /bin/sh $(HOME)/project/config/missing --run autoconf > FATAL ERROR: Autoconf version 2.54 or higher is required for this > script > > Now.. either I've got it completely wrong in my head or autoconf on a > "user" PC should be needed only if configure.in/Makefile.am are > modified? Maybe a problem with the granularity of Windows filetimes? I believe that autoreconf isn't entirely reliable. This is the reason that projects (e.g. libgetopt++) often have a bootstrap.sh which runs the relevant autotools. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
cygwin's autoconf?
Hi! Finally I decided to study seriously the autotools (thanks for the references, Nicholas!).. but I have a small problem: (cyberone is my CygWin/WinXP desktop machine, cyberx is my FreeBSD home-server machine) cyberone$ autoreconf cyberone$ rsync -vrLe ssh --delete * lapo@cyberx:project/ cyberx$ ./configure [normal configure output] cyberx$ make cd . && /bin/sh $(HOME)/project/config/missing --run autoconf FATAL ERROR: Autoconf version 2.54 or higher is required for this script Now.. either I've got it completely wrong in my head or autoconf on a "user" PC should be needed only if configure.in/Makefile.am are modified? Maybe a problem with the granularity of Windows filetimes? -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) smime.p7s Description: S/MIME Cryptographic Signature
RE: [ANNOUNCEMENT] Updated: zsh-4.0.6-1
> From: Peter A. Castro > > Some additions for Cygwin: > - Added a default /etc/zprofile. If you already have a custom > /etc/zprofile, please save yours some place before installing. I think it would have been better for you to have a /etc/zprofile.default and a /etc/postinstall/zprofile.sh script which checks for the [none] existance of /etc/zprofile, in which case it cp /etc/zprofile.default /etc/zprofile the same as /etc/profile Just my 2p worth ;) J. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Missing getopt.h for MinGW is not a bug.
> -Original Message- > From: Robert Collins [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 26, 2002 5:14 AM > To: Earnie Boyd > Cc: [EMAIL PROTECTED] > Subject: Re: Missing getopt.h for MinGW is not a bug. > > > On Tue, 2002-11-26 at 23:58, Earnie Boyd wrote: > > We purposefully do not give GPLed interfaces to the MinGW user > > community, even though we do supply the libraries for those who are > > aware of the GPL issues. You'll have to supply your own declarations > > for getopt. > > There are BSD getopt's floating around, why not use one of those? The one included with cygwin (/usr/include/getopt.h) is a BSD licensed header file. > > If I'm putting my nose in a can of worms, just say so :}. Ditto. > > Rob > -- > --- > GPG key available at: http://users.bigpond.net.au/robertc/keys.txt. > --- > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
