Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
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> <am3dogh7cg DOT fsf AT sauerkraut-und-lederhosen DOT e DOT kth DOT se> <20000420162205 DOT B2308 AT cygnus DOT com> <amu2gwfr3x DOT fsf AT sauerkraut-und-lederhosen DOT e DOT kth DOT se> <20000420174130 DOT B3346 AT cygnus DOT com>
From: Love <lha AT stacken DOT kth DOT se>
Date: 21 Apr 2000 09:58:41 +0200
In-Reply-To: Chris Faylor's message of "Thu, 20 Apr 2000 17:41:30 -0400"
Message-ID: <amd7nj9972.fsf@sauerkraut-und-lederhosen.e.kth.se>
Lines: 31
User-Agent: Gnus/5.0803000000000003 (Gnus v5.8.3) Emacs/20.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Chris Faylor <cgf AT cygnus DOT com> writes:

> On Thu, Apr 20, 2000 at 10:35:14PM +0200, Love wrote:
> >Chris Faylor <cgf AT cygnus DOT com> writes:
> >
> >> >I can give you a tarboll with binaries that cause the error.
> >> 
> >> Sorry.  I definitely don't have time to debug individual problems.
> >
> >Sure, I'll happly try to find it out myself, I currenly trying to build a
> >libcygwin1.dll with debugging symbols.
> 
> 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.

Ok, so you mean that Visual C just tells me where the exception should be
handled but wasn't ? It looked on the assembely that it really did the
*(int *)0x4 = N; in cygwin1.dll. But then I'm not that good on i386
assembly.
 
Thanks for the tips.

> If I were you, I would just debug your program in the normal way before
> going to the effort of building cygwin.

Well I build it, no problem there. Are you using /cygdrive/c/cygwin as
prefix when building the release ?

Love

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com