From: ralf@uni-koblenz.de
To: Mike Shaver <shaver@netscape.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: mozilla on the Indy
Date: Mon, 6 Jul 1998 20:31:53 +0200 [thread overview]
Message-ID: <19980706203153.03930@uni-koblenz.de> (raw)
In-Reply-To: <35A10B96.9B47C150@netscape.com>; from Mike Shaver on Mon, Jul 06, 1998 at 01:38:30PM -0400
On Mon, Jul 06, 1998 at 01:38:30PM -0400, Mike Shaver wrote:
> ralf@uni-koblenz.de wrote:
> > Now that I've taken myself two minutes to browse your attached sources -
> > the patches to the NSPR thread routines look suspicious. The are
> > playing games with the frame pointer which at least on the first look
> > don't make sense as gcc automatically enables -fomit-frame-pointer when
> > optimizing.
>
> Turns out it's there only to save the FP so that you can use gdb to look
> at the NSPR thread stacks during debugging. So, the fact that gcc
> removes it when building optimized isn't a problem.
>
> For the record, NSPR threads aren't clone() threads; they're
> setjmp/longjmp things.
Usless effort, on MIPS debugging works without having a frame pointer.
RalF
next prev parent reply other threads:[~1998-07-06 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-01 14:15 mozilla on the Indy Mike Shaver
1998-07-01 15:54 ` ralf
1998-07-02 2:11 ` ralf
1998-07-06 17:38 ` Mike Shaver
1998-07-06 18:31 ` ralf [this message]
1998-07-05 0:31 ` ralf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19980706203153.03930@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux@cthulhu.engr.sgi.com \
--cc=shaver@netscape.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox