public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
* RemoteFrame vs StackFrame
@ 2007-05-07 14:09 Nurdin Premji
  2007-05-09  6:19 ` Nurdin Premji
  0 siblings, 1 reply; 3+ messages in thread
From: Nurdin Premji @ 2007-05-07 14:09 UTC (permalink / raw)
  To: frysk

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: RemoteFrame vs StackFrame
  2007-05-07 14:09 RemoteFrame vs StackFrame Nurdin Premji
@ 2007-05-09  6:19 ` Nurdin Premji
  2007-05-14 16:16   ` Nurdin Premji
  0 siblings, 1 reply; 3+ messages in thread
From: Nurdin Premji @ 2007-05-09  6:19 UTC (permalink / raw)
  To: Nurdin Premji; +Cc: frysk

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.)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: RemoteFrame vs StackFrame
  2007-05-09  6:19 ` Nurdin Premji
@ 2007-05-14 16:16   ` Nurdin Premji
  0 siblings, 0 replies; 3+ messages in thread
From: Nurdin Premji @ 2007-05-14 16:16 UTC (permalink / raw)
  To: frysk

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-05-11 15:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-07 14:09 RemoteFrame vs StackFrame Nurdin Premji
2007-05-09  6:19 ` Nurdin Premji
2007-05-14 16:16   ` Nurdin Premji

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).