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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com X-Authentication-Warning: sauerkraut-und-lederhosen.e.kth.se: lha set sender to lha AT s3 DOT kth DOT se using -f To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: PS1, gdb and other trubbels References: <200004201759 DOT TAA02478 AT sauerkraut-und-lederhosen DOT e DOT kth DOT se> <20000420144815 DOT A1549 AT cygnus DOT com> <20000420162205 DOT B2308 AT cygnus DOT com> <20000420174130 DOT B3346 AT cygnus DOT com> From: Love Date: 21 Apr 2000 14:08:09 +0200 In-Reply-To: Love's message of "21 Apr 2000 09:58:41 +0200" Message-ID: Lines: 17 User-Agent: Gnus/5.0803000000000003 (Gnus v5.8.3) Emacs/20.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Love writes: > > You should be able to set breakpoints in gdb to find out where the > > problem is occurring. The fact that cygwin shows up on a stack trace > > does not mean that the problem is in cygwin. Cygwin intercepts all of > > the Windows "signals" in order to properly emulate UNIX signals. > > Thanks for the tips. But you're right, there is some weirdo stuff going on in my lwp-on-pthread-on-windows-threads emulation package that I wrote previously. It works with our old thread package that does the stack switching itself. Guess I'll have to fix pthreads in cygwin some way... Thanks for the new gdb, works great. Love -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com