[1.7] problems with subversion
When running svn commands (say, svn status or svn checkout) I'm getting the following error: /usr/bin/svn.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory In attempt to isolate the problem, I reinstalled Cygwin 1.7 from scratch, adding only two extra packages (on top of the default packages chosen by the setup tool): subversion and openssh. I then tried to run svn checkout (using svn+ssh) and got the same error message. Any suggestions? Thanks, Yuval -- 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
1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
Recently, when trying to run various programs (e.g., xterm, emacs, subversion), I often get a message of the following type: 4 [main] xterm 4640 exception::handle: Exception: STATUS_ACCESS_VIOLATION 496 [main] xterm 4640 open_stackdumpfile: Dumping stack trace to xterm.exe.stackdump The context of the file xterm.exe.stackdump is: Exception: STATUS_ACCESS_VIOLATION at eip=610202F7 eax=00CE00F8 ebx=61229E44 ecx=7530783F edx=002D20F0 esi= edi=0022FA14 ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 4640, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args End of stack trace In attempt to pin down the problem, I reinstalled cygwin from scratch, using setup.exe with noting but the default setting + xinit. When trying to open an xterm window (from an existing one) I often get the aforementioned message. (In fact, many times I get multiple copies of these two lines.) I think that this problem has nothing to do with the problem reported to be solved in http://sourceware.org/ml/cygwin/2010-01/msg00632.html This is because: (1) the tsaware flag is set for xterm; and (2) my windows 7 is in "Turn on DEP for essential Windows programs and services only" mode. Any suggestions? Thanks, Yuval The cygcheck.out and /var/log/XWin.0.log files are attached. cygcheck.out Description: Binary data XWin.0.log Description: Binary data -- 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: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
wrote:
> On Mon, Apr 19, 2010 at 02:20:48AM +0100, Dave Korn wrote:
>>On 18/04/2010 23:09, Yuval Emek wrote:
>>
>>> The context of the file xterm.exe.stackdump is:
>>> Exception: STATUS_ACCESS_VIOLATION at eip=610202F7
>>> eax=00CE00F8 ebx=61229E44 ecx=7530783F edx=002D20F0 esi=
>>> edi=0022FA14
>>> ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 4640, thread
>>> main
>>> cs=001B ds=0023 es=0023 fs=003B gs= ss=0023
>>> Stack trace:
>>> Frame Function Args
>>> End of stack trace
>>
>>$ addr2line --exe cygwin-1.7.5-1/winsup/cygwin/cygwin1.dbg
>>610202F7
>>/ext/build/netrel/src/cygwin-1.7.5-1/winsup/cygwin/dll_init.cc:78
>>
>> 71 /* Initialize an individual DLL */
>> 72 int
>> 73 dll::init ()
>> 74 {
>> 75 int ret = 1;
>> 76
>> 77 /* Why didn't we just import this variable? */
>> 78 *(p.envptr) = __cygwin_environ;
>> 79
>>
>> Ah. Hmm. That certainly does look like it's nothing to do with the DEP or
>>anything else; either we're missing a null pointer check here, or there's some
>>reason why that pointer's never supposed to be null at this point in the code
>>but somehow it is.
>
> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
> in cygwin_attach_dll. It is supposed to be set to the address of the
> "environ" variable in the DLL. It is not supposed to be NULL. That
> assignment should actually not even be necessary but the fact that
> envptr may be NULL is a problem. Of course, it could just be some
> non-NULL garbage too. Running in gdb and getting a stack trace would be
> instructive.
Can you be more specific? (I have been using cygwin for a while, but I
never debugged it beforehand.)
I can install gdb using setup.exe . What should I do then in order to
obtain a stack trace?
Thanks,
Yuval
>
> The handling of the environ pointer has always made my head hurt. In
> retrospect, I wish I'd simplified it for 1.7.x.
>
> cgf
>
> --
> 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
>
>
--
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: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote: > On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote: >>On 4/19/2010 7:44 AM, Yuval Emek wrote: >>> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor >>> wrote: >> ^ >><http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Feeding spammers just makes >>them hungry. >> >> >> >>>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common >>>> in cygwin_attach_dll. It is supposed to be set to the address of the >>>> "environ" variable in the DLL. It is not supposed to be NULL. That >>>> assignment should actually not even be necessary but the fact that >>>> envptr may be NULL is a problem. Of course, it could just be some >>>> non-NULL garbage too. Running in gdb and getting a stack trace would be >>>> instructive. >>> >>> Can you be more specific? (I have been using cygwin for a while, but I >>> never debugged it beforehand.) >>> I can install gdb using setup.exe . What should I do then in order to >>> obtain a stack trace? >> >>Grab a snapshot from <http://cygwin.com/snapshots/>. You want the DLL >>and debugging info at least. > > And, assuming that you can actually run gdb, just "gdb bash" and then "r". I installed gdb and then downloaded the (latest) snapshots of cygwin1.dll and cygwin1.dbg and extracted then to /bin/ (replacing the previous cygwin1.dll) . Running gdb bash seems to fail since there are no debugging symbols. In particular, when typing r in the gdb prompt, I get the following output: Starting program: /usr/bin/bash [New thread 3800.0x15b4] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New thread 3800.0x13f4] [1]+ Stopped gdb bash (Makes sense, I guess, as bash was not compiled with debugging info.) Can I download debugging info for bash from somewhere? (As far as I understand, I don't even have the source code for bash.) Is there something else I can do? > > cgf > > -- > 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 > > -- 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
1.7.5-1: a problem with mkgroup
When invoking a cygwin bash shell window, I'm getting the following message: ***message begins*** Your group is currently "mkgroup". This indicates that neither your gid nor your pgsid (primary group associated with your SID) is in /etc/group. The /etc/group (and possibly /etc/passwd) files should be rebuilt. See the man pages for mkpasswd and mkgroup then, for example, run mkpasswd -l [-d] > /etc/passwd mkgroup -l [-d] > /etc/group Note that the -d switch is necessary for domain users. ***message ends*** An attempt to run mkgroup ends in: $ mkgroup SYSTEM:S-1-5-18:18: mkgroup (101): [1355] The specified domain either does not exist or could not be contacted. The content of my /etc/group file is: $ cat /etc/group root:S-1-5-32-544:0: SYSTEM:S-1-5-18:18: Administrators:S-1-5-32-544:544: Backup Operators:S-1-5-32-551:551: Cryptographic Operators:S-1-5-32-569:569: Distributed COM Users:S-1-5-32-562:562: Event Log Readers:S-1-5-32-573:573: Guests:S-1-5-32-546:546: IIS_IUSRS:S-1-5-32-568:568: Network Configuration Operators:S-1-5-32-556:556: Performance Log Users:S-1-5-32-559:559: Performance Monitor Users:S-1-5-32-558:558: Power Users:S-1-5-32-547:547: Remote Desktop Users:S-1-5-32-555:555: Replicator:S-1-5-32-552:552: Users:S-1-5-32-545:545: Offer Remote Assistance Helpers:S-1-5-21-11240-2348469801-2904254719-1005:10 05: None:S-1-5-21-11240-2348469801-2904254719-513:513: An attempt to run mkpasswd ends in: $ mkpasswd SYSTEM:*:18:544:,S-1-5-18:: LocalService:*:19:544:U-NT AUTHORITY\LocalService,S-1-5-19:: NetworkService:*:20:544:U-NT AUTHORITY\NetworkService,S-1-5-20:: Administrators:*:544:544:,S-1-5-32-544:: mkpasswd (102): [1355] The specified domain either does not exist or could not b e contacted. The content of my /etc/passwd file is: $ cat /etc/passwd SYSTEM:*:18:544:,S-1-5-18:: LocalService:*:19:544:U-NT AUTHORITY\LocalService,S-1-5-19:: NetworkService:*:20:544:U-NT AUTHORITY\NetworkService,S-1-5-20:: Administrators:*:544:544:,S-1-5-32-544:: Admin:unused:1001:513:Admin,U-YUVALEM-W7\Admin,S-1-5-21-11240-2348469801-290 4254719-1001:/home/Admin:/bin/bash Administrator:unused:500:513:U-YUVALEM-W7\Administrator,S-1-5-21-11240-23484 69801-2904254719-500:/home/Administrator:/bin/bash Guest:unused:501:513:U-YUVALEM-W7\Guest,S-1-5-21-11240-2348469801-2904254719 -501:/home/Guest:/bin/bash i-yuvale:unused:123982:10513:U-MIDDLEEAST\i-yuvale,S-1-5-21-72051607-1745760036- 109187956-113982:/home/i-yuvale:/bin/bash The above phenomenon occurs with a fresh cygwin installation (using setup.exe with the default packages) on my Windows 7. It may be related to another problem I'm experiencing (reported in http://cygwin.com/ml/cygwin/2010-04/msg00740.html) in some mysterious (and obviously indirect) manner. Any suggestions? The output of running cygcheck -s -v -r is attached. cygcheck.out Description: Binary data -- 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: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
Is it possible that this problem is somehow related to another problem I'm experiencing, reported in http://cygwin.com/ml/cygwin/2010-04/msg00797.html ? On Tue, Apr 20, 2010 at 09:19, Yuval Emek wrote: > On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote: >> On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote: >>>On 4/19/2010 7:44 AM, Yuval Emek wrote: >>>> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor >>>> wrote: >>> ^ >>><http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Feeding spammers just makes >>>them hungry. >>> >>> >>> >>>>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common >>>>> in cygwin_attach_dll. It is supposed to be set to the address of the >>>>> "environ" variable in the DLL. It is not supposed to be NULL. That >>>>> assignment should actually not even be necessary but the fact that >>>>> envptr may be NULL is a problem. Of course, it could just be some >>>>> non-NULL garbage too. Running in gdb and getting a stack trace would be >>>>> instructive. >>>> >>>> Can you be more specific? (I have been using cygwin for a while, but I >>>> never debugged it beforehand.) >>>> I can install gdb using setup.exe . What should I do then in order to >>>> obtain a stack trace? >>> >>>Grab a snapshot from <http://cygwin.com/snapshots/>. You want the DLL >>>and debugging info at least. >> >> And, assuming that you can actually run gdb, just "gdb bash" and then "r". > > I installed gdb and then downloaded the (latest) snapshots of > cygwin1.dll and cygwin1.dbg and extracted then to /bin/ (replacing the > previous cygwin1.dll) . > Running gdb bash seems to fail since there are no debugging symbols. > In particular, when typing r in the gdb prompt, I get the following > output: > > Starting program: /usr/bin/bash > [New thread 3800.0x15b4] > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > [New thread 3800.0x13f4] > > [1]+ Stopped gdb bash > > (Makes sense, I guess, as bash was not compiled with debugging info.) > Can I download debugging info for bash from somewhere? (As far as I > understand, I don't even have the source code for bash.) > Is there something else I can do? > >> >> cgf >> >> -- >> 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 >> >> > -- 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: 1.7.5-1: a problem with mkgroup
On Wed, Apr 21, 2010 at 00:43, Larry Hall (Cygwin) wrote: > On 4/20/2010 9:38 AM, Yuval Emek wrote: >> >> When invoking a cygwin bash shell window, I'm getting the following >> message: >> ***message begins*** >> Your group is currently "mkgroup". This indicates that neither >> your gid nor your pgsid (primary group associated with your SID) >> is in /etc/group. >> >> The /etc/group (and possibly /etc/passwd) files should be rebuilt. >> See the man pages for mkpasswd and mkgroup then, for example, run >> >> mkpasswd -l [-d]> /etc/passwd >> mkgroup -l [-d]> /etc/group >> >> Note that the -d switch is necessary for domain users. >> ***message ends*** >> >> An attempt to run mkgroup ends in: >> $ mkgroup >> SYSTEM:S-1-5-18:18: >> mkgroup (101): [1355] The specified domain either does not exist or could >> not be contacted. > > According to your cygcheck output says you have an old installation in > 'd:\cygwin-old'. If true, please remove this and then run: > > cygcheck --delete-orphaned-installation-keys This is very strange mainly because I don't have (and I never had) a D:\ partition on my laptop. (How did you extract this info from my cygcheck output btw?) Running cygcheck --delete-orphaned-nstallation-keys and then reinstalling everything (with setup.exe) didn't work. However, running cygcheck --delete-orphaned-nstallation-keys, uninstalling cygwin entirely (by following the instructions in http://cygwin.com/faq/faq-nochunks.html#faq.setup.uninstall-all), and then installing it from scratch did work (hooray)! So, this problem is solved (thanks), but the problem I reported in http://cygwin.com/ml/cygwin/2010-04/msg00740.html remains (back to that thread). Yuval > > Then reinstall Cygwin in it's current location (just re-run "setup.exe" > and specify "Reinstall" for "All". Your current installation is > incomplete, presumably because of some conflict with your "old" > installation. > > -- > Larry Hall http://www.rfk.com > RFK Partners, Inc. (508) 893-9779 - RFK Office > 216 Dalton Rd. (508) 893-9889 - FAX > Holliston, MA 01746 > > _ > > A: Yes. >> >> Q: Are you sure? >>> >>> A: Because it reverses the logical flow of conversation. >>>> >>>> Q: Why is top posting annoying in email? > > -- > 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 > > -- 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: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
On Tue, Apr 20, 2010 at 17:26, Christopher Faylor wrote: > > On Tue, Apr 20, 2010 at 09:19:28AM +0300, Yuval Emek wrote: > >On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote: > >> On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote: > >>>On 4/19/2010 7:44 AM, Yuval Emek wrote: > >>>> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor > >>>> ?wrote: > >>> ? ?^ > >>><http://cygwin.com/acronyms/#PCYMTNQREAIYR>. ?Feeding spammers just makes > >>>them hungry. > >>> > >>> > >>> > >>>>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common > >>>>> in cygwin_attach_dll. ?It is supposed to be set to the address of the > >>>>> "environ" variable in the DLL. ?It is not supposed to be NULL. ?That > >>>>> assignment should actually not even be necessary but the fact that > >>>>> envptr may be NULL is a problem. ?Of course, it could just be some > >>>>> non-NULL garbage too. ?Running in gdb and getting a stack trace would be > >>>>> instructive. > >>>> > >>>> Can you be more specific? (I have been using cygwin for a while, but I > >>>> never debugged it beforehand.) > >>>> I can install gdb using setup.exe . What should I do then in order to > >>>> obtain a stack trace? > >>> > >>>Grab a snapshot from <http://cygwin.com/snapshots/>. ?You want the DLL > >>>and debugging info at least. > >> > >> And, assuming that you can actually run gdb, just "gdb bash" and then "r". > > > >I installed gdb and then downloaded the (latest) snapshots of > >cygwin1.dll and cygwin1.dbg and extracted then to /bin/ (replacing the > >previous cygwin1.dll) . > >Running gdb bash seems to fail since there are no debugging symbols. > >In particular, when typing r in the gdb prompt, I get the following > >output: > > > >Starting program: /usr/bin/bash > >[New thread 3800.0x15b4] > >(no debugging symbols found) > >(no debugging symbols found) > >(no debugging symbols found) > >[New thread 3800.0x13f4] > > > >[1]+ Stopped gdb bash > > > >(Makes sense, I guess, as bash was not compiled with debugging info.) > >Can I download debugging info for bash from somewhere? (As far as I > >understand, I don't even have the source code for bash.) > >Is there something else I can do? > > I'm not interested in bash symbols. > > In the above it sounds like you may actually be running gdb from bash. > > I suggested bash because I thought most cygwin programs were dying but, > on rereading the original report, you only mentioned xterm, emacs, and > subversion. So, the thing to try would be to run gdb on one of those > from a c:\> prompt. And, it really would be as simple as just typing: > > gdb svn > r > bt > > and reporting the backtrace. > > cgf > I cannot produce a backtrace: I run gdb on emacs (from a dos command prompt). Then I set the arguments of emacs to --batch -l bar.el (which causes the aforementioned exception many times) and type run. In 2 out of three runs, I get a message that looks like: ***message begins*** Starting program: /cygdrive/c/cygwin/bin/emacs --batch -l bar.el [New thread 4980.0x14dc] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New thread 4980.0x1600] warning: ERROR !!! HeapSetInformation failed to set g_Heap to LFH warning: ERROR !!! HeapSetInformation failed to set g_SpyHeap to LFH [New thread 4980.0x798] [New thread 4980.0xdc0] warning: Lowest section in /cygdrive/c/Windows/system32/security.dll is .text at 00401000 [New thread 4980.0x1410] [New thread 4980.0x1700] (No files need saving) [New thread 4980.0xe24] 5 [main] emacs-X11 4040 exception::handle: Exception: STATUS_ACCESS_VIOLAT ION 723 [main] emacs-X11 4040 open_stackdumpfile: Dumping stack trace to emacs-X 11.exe.stackdump 8 [main] emacs-X11 2056 exception::handle: Exception: STATUS_ACCESS_VIOLAT ION 743 [main] emacs-X11 2056 open_stackdumpfile: Dumping stack trace to emacs-X 11.exe.stackdump 6 [main] emacs-X11 2948 exception::handle: Exception: STATUS_ACCESS_VIOLAT ION 719 [main] emacs-X11 2948 open_stackdumpfile: Dumping stack trace to emacs-X 11.exe.stackdump 6 [main] emacs-X11 1100 exception::handle: Exception: STATUS_ACCESS_VIOLAT ION 739 [main] emacs-X11 1100 open_stackdumpfile: Dumping stack trace to emacs-X 11.exe.stackdump [New thread 4980.0x12b8]
