Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Lotus-FromDomain: JPMORGAN AT SMTP From: "Noel L Yap" To: cygwin AT cygwin DOT com Message-ID: <85256AA3.007B0FCA.00@nyc-ntgw-n01.ny.jpmorgan.com> Date: Thu, 9 Aug 2001 18:24:13 -0400 Subject: Re: memory problems in chroot'ed env (Was: chroot bug) Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline I haven't been able to get to happen when using "chroot /", but here's output from one of my sessions that did reproduce the "cannot allocate" problem: nyap:jpmpsdev AT NYAP:~> chroot /view/nyap-tig-du nyap:jpmpsdev AT NYAP:~> ls .Xdefaults .bashrc~ .inputrc aoeu~ proj/ .Xdefaults~ .clearcase_profile@ .inputrc-0 app-defaults/ tmp/ .bash/ .clearcase_profile~ .inputrc~ bin/ view/ .bash_history .emacs .saves-670-NYAP~ lisp/ .bashrc .emacs~ .viminfo msfe/ nyap:jpmpsdev AT NYAP:~> cd /vobs nyap:jpmpsdev AT NYAP:/vobs|nyap-tig-du> ls admin/ ds/ opt/ picms/ play/ stage/ tk/ cccq/ fastcmp/ pi/ picmsdemo/ rel/ tiga/ nyap:jpmpsdev AT NYAP:/vobs|nyap-tig-du> cd ds /vobs/ds nyap:jpmpsdev AT NYAP:/vobs/ds|nyap-tig-du> ls labmorgan/ lost+found/ tig/ nyap:jpmpsdev AT NYAP:/vobs/ds|nyap-tig-du> cleartool pwv Working directory view: nyap-tig-du Set view: ** NONE ** nyap:jpmpsdev AT NYAP:/vobs/ds|nyap-tig-du> ls bash: xmalloc: cannot allocate 3646 bytes (0 bytes allocated) nyap:jpmpsdev AT NYAP:/vobs/ds|nyap-tig-du> ls labmorgan/ lost+found/ tig/ nyap:jpmpsdev AT NYAP:/vobs/ds|nyap-tig-du> cleartool pwv Working directory view: nyap-tig-du Set view: ** NONE ** nyap:jpmpsdev AT NYAP:/vobs/ds|nyap-tig-du> ls labmorgan/ lost+found/ tig/ nyap:jpmpsdev AT NYAP:/vobs/ds|nyap-tig-du> mount d:\opt\Rational\ClearCase\4.0 on /usr/atria type user (binmode) d:\opt\Rational\ClearCase\4.0 on /view/nyap-tig-du/usr/atria type user (textmode) v:\nyap-tig-du on /view/nyap-tig-du/vobs type user (binmode) d:\cygwin\bin on /usr/bin type user (binmode) d:\cygwin\lib on /usr/lib type user (binmode) d:\cygwin on / type user (binmode) d:\cygwin on /view/nyap-tig-du type user (binmode) h: on /home/nyap type user (textmode) h: on /view/nyap-tig-du/home/nyap type user (textmode) v: on /view type user (binmode) c: on /%/c type user (binmode,noumount) d: on /%/d type user (binmode,noumount) f: on /%/f type user (binmode,noumount) g: on /%/g type user (binmode,noumount) s: on /%/s type user (binmode,noumount) t: on /%/t type user (binmode,noumount) u: on /%/u type user (binmode,noumount) z: on /%/z type user (binmode,noumount) Can you give me some hints as to how I can track this down any further, please? Thanks, Noel On Thu, Aug 09, 2001 at 09:20:19AM -0400, Noel L Yap wrote: >chroot works for the most part. I get sporadic memory errors (xmalloc not able >to allocate or segfault) when trying out commands (eg ls) after the chroot, >though. I'll see if I can track them down. What is the chroot command that you're using "chroot /"? Since this actually does nothing at all now it would be surprising if it had any effect on any commands. Details in bug reports are always a necessity if you want solutions. 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/ This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. -- 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/