public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu> To: cygwin-xfree@cygwin.com Subject: Re: Crash in xserv 4.3.0-40 Date: Thu, 15 Jan 2004 23:02:00 -0000 [thread overview] Message-ID: <40071C00.9080201@msu.edu> (raw) In-Reply-To: <1074201974.25360.81.camel@famine> Ãyvind, Ãyvind Harboe wrote: > Hi Harold, > > I'll be sure to follow up on your latest testing tips. Okay. > Q: is there any reason not to include symbol information in your testing builds? I have seen people asking this since -39 was posted (I believe). There must be some confusion, because -39 and -40 are not 'test' builds. They are 'curr'. So, including symbol information the testing builds wouldn't help with your problem... you have an observed crash in the 'curr' build, not a 'test' build. With that being said, I'll address the issue of symbol information: 1) If I include symbol information and there are no crashes, then people will complain (don't argue with me, they *will* complain) about the size of the download being X KB larger than it had to be. 2) If I do include symbol information and there are crashes, then only once every year or so will someone actually bother to do a proper debug for me anyhow. 3) A non-stripped build of XWin.exe isn't particularly useful... I generally already know which function the crash is in. Anything short of a line number won't do me much good. 4) Getting line numbers from users and cross checking my source files to make sure that I've got the right source, plus keeping around an elaborate system of stored releases, etc. is not something that I care to do. Thus, there won't be much good for people to send me stackdumps, etc. I'm not going to change this because I have defined an upper limit on how much time I will spend on Cygwin/X stuff and I am already *way* over that limit. Feel free to start performing this service yourself. I don't think it will get much use, then you will figure out why I am not interested in it :) 5) Including full debug symbols (-g) isn't possible with my current setup inless I keep my debug build tree up to date, which is tough since I'm doing so much work on other things that my CPU is usually pegged at 100%. I don't have extra time to be doing debug builds of XWin.exe in addition to the standard builds. I have no interest in doing a debug build as the default and stripping the executables either. Just not interested in that since it takes more disk space and is slower (probably due to I/O limitations). So, if anyone sees someone else asking about debug symbols, please crack them upside the head for me so I don't have to say all of this again. > Read on.... > > > However, here are the latest and greatest: > > - I'm pretty sure that the crash isn't there when I compiled and installed the > sources as I described. > - I've recently discovered core dumps! Here is a post > that describes it a bit: http://www.cygwin.com/ml/cygwin-patches/2000-q3/msg00041.html This looks a heck of a lot more useful than including massive amounts of symbols. I have always wanted to look into core dumps further, but haven't had a chance yet. > So, > > armed with core dumps, my strategy is as follows: > > - uninstall everything and reinstall cygwin from scratch w/latest xserv. Interesting note of the day: if you are doing local builds of Cygwin/X and installing them to test things, do what I do: 1) Rename /usr/X11R6 to /usr/X11R6_default 2) Rename /etc/X11 to /etc/X11_default 3) If you didn't build the fonts (saves about an hour), then *cut* the following directory in Windows Explorer and paste it in the second directory: /usr/X11R6_default/lib/X11/fonts /usr/X11R6/lib/X11/fonts 4) Test away 5) When you want to revert, or temporarily revert, just move your directories out of the way: /usr/X11R6 -> /usr/X11R6_local /usr/X11R6_default -> /usr/X11R6 /etc/X11 -> /etc/X11_local /etc/X11_default -> /etc/X11 Cut /usr/X11R6_local/lib/X11/fonts and paste /usr/X11R6/lib/X11/fonts 6) That way you don't screw up your Cygwin installation and you don't have to keep reinstalling things when you are done testing for a little bit. The reason I cut and paste the fonts directory is because it contains thousands of files; it takes anywhere from 20 minutes to an hour just to copy that many files on Win32. Cutting and pasting is instantaneous. > - add the following line to the beginning of startxwin.bat > > set cygwin=error_start=c:\cygwin\bin\dumper.exe > > - wait for the crash > - Recompile w/debug info > - Wait for crash > - Coredump anyone? :-) Cool, let us know how it goes. Harold
next prev parent reply other threads:[~2004-01-15 23:02 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-15 21:26 Øyvind Harboe 2004-01-15 22:25 ` enableing GL overlays Bruce Dobrin 2004-01-15 22:41 ` Alexander Gottwald 2004-01-15 23:02 ` Harold L Hunt II [this message] 2004-01-15 23:06 ` Crash in xserv 4.3.0-40 Christopher Faylor 2004-01-16 5:27 ` Earle F. Philhower III -- strict thread matches above, loose matches on Subject: below -- 2004-01-14 15:15 Øyvind Harboe 2004-01-14 12:36 Øyvind Harboe 2004-01-14 13:52 ` Kensuke Matsuzaki 2004-01-13 23:02 Øyvind Harboe 2004-01-15 17:52 ` Harold L Hunt II 2004-01-13 17:21 Øyvind Harboe 2004-01-13 16:24 Øyvind Harboe 2004-01-13 17:01 ` Harold L Hunt II 2004-01-13 14:20 Øyvind Harboe
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=40071C00.9080201@msu.edu \ --to=huntharo@msu.edu \ --cc=cygwin-xfree@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: linkBe 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).