From: Nurdin Premji <npremji@redhat.com>
To: frysk@sourceware.org
Subject: Re: RemoteFrame vs StackFrame
Date: Mon, 14 May 2007 16:16:00 -0000 [thread overview]
Message-ID: <46448DE4.5040901@redhat.com> (raw)
In-Reply-To: <4640B2F3.20405@redhat.com>
Nurdin Premji wrote:
> Nurdin Premji wrote:
>> frysk.rt.RemoteFrame uses the cross-platform enabled libunwind
>> bindings, to enable frysk to use these bindings simply set
>> frysk.rt.StackFactory.remoteUnwind to true.
>>
>> The RemoteFrame passes all core tests but trying to start the source
>> window causes it to abort.
> Fixed the issue with the source window aborting (had to do with
> aggressive garbage collection). Now the only issue is that RemoteFrame
> takes about 15 seconds or so to open the source window, while
> StackFrame takes 3-5.
> (On a dell optiplex gx 280 = 3.4 ghz pentium 4, 1.5 GB ram.)
The switch has been flipped and now all code should (transparently) be
switched over to RemoteFrame.
Fixed the slowdown, RemoteFrame.getOuter was not checking the cached
outer frame before trying to unwind.
prev parent reply other threads:[~2007-05-11 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 14:09 Nurdin Premji
2007-05-09 6:19 ` Nurdin Premji
2007-05-14 16:16 ` Nurdin Premji [this message]
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=46448DE4.5040901@redhat.com \
--to=npremji@redhat.com \
--cc=frysk@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).