Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Chris January" To: Subject: RE: 1.5.5s: procps error Date: Tue, 16 Sep 2003 22:13:25 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <16231.15888.50020.29068@phish.entomo.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 I'll look into this in due time. > -----Original Message----- > From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf > Of David Rothenberger > Sent: 16 September 2003 17:45 > To: cygwin@cygwin.com > Subject: Re: 1.5.5s: procps error > > > David Rothenberger writes: > > FWIW, the latest snapshot and the latest CVS both cause a problem > > with procps that is not present in 1.5.4. > > > > ---------------------------------------------------------------------- > > $ procps > > > > > > Signal 11 caught by ps (procps version 2.0.7). > > Please send bug reports to > > ---------------------------------------------------------------------- > > I modified procps slightly to avoid catching signal 11, so a > stackdump file would be created. It's attached, with each address > in the stack decoded with addr2line. This was done with using the > latest CVS sources for cygwin1.dll. > > Dave > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/