Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 28 Oct 2004 12:24:24 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: jdeifik <jdeifik AT weasel DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Problem with pthead.h - child's thread ending, causes main program to exit
In-Reply-To: <6.1.2.0.0.20041028090536.01e9c470@localhost>
Message-ID: <Pine.GSO.4.61.0410281221200.11727@slinky.cs.nyu.edu>
References: <6 DOT 1 DOT 2 DOT 0 DOT 0 DOT 20041027164547 DOT 01cffec0 AT localhost> <Pine DOT CYG DOT 4 DOT 58 DOT 0410280941080 DOT 2868 AT fordpc DOT vss DOT fsi DOT com> <6 DOT 1 DOT 2 DOT 0 DOT 0 DOT 20041028090536 DOT 01e9c470 AT localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; X-AVG-CHECKED=avg-ok-55024AC5; CHARSET=US-ASCII; FORMAT=flowed
Content-ID: <Pine DOT GSO DOT 4 DOT 61 DOT 0410281221202 DOT 11727 AT slinky DOT cs DOT nyu DOT edu>
X-Scanned-By: MIMEDefang 2.39

On Thu, 28 Oct 2004, jdeifik wrote:

> > On Wed, 27 Oct 2004, jdeifik wrote:
> >
> > > When I run the program with gdb, I get really weird segmentation
> > > faults, for example:
> >
> > http://www.cygwin.com/ml/cygwin/2004-10/msg01033.html

Does anyone know gdb macros well enough to say off-hand whether it's
possible to write a function to ignore those particular SEGVs?

> > > Program received signal SIGSEGV, Segmentation fault.
> > > [Switching to thread 3280.0xcdc]
> > > 0x610b479d in random () from /usr/bin/cygwin1.dll
> > [snip]
> > > The details of the backtrace vary a bit, but always start off in
> > > random in cygwin1.dll
> >
> > You can not trust the back trace from a stripped cygwin1.dll.  You must
> > compile your own with debugging symbols if you want to see a valid trace
> > into it.  (Hint: random is NOT where your problem is)
>
> Ok, then perhaps a non-stripped cygwin1.dll should be supplied by default
> so gdb can see what is happening.

There was a discussion a while ago about providing debugging symbols for
various versions of cygwin1.dll (both the releases and the snapshots).
Did it ever come to any conclusion?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

--
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/