Nabble - FXRuby Users

Re: Set active only one window

2008-10-04T23:57:28Z

Hi Vladimir,

Thank you! This is just what I wanted.
--
Regards

Soumya

----- Original Message ----
From: Vladimir Konrad <v.konrad@...>
To: fxruby-users@...
Sent: Friday, 3 October, 2008 15:21:15
Subject: Re: [fxruby-users] Set active only one window

One possible way to do log-in attached...

Vlad

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Re: Set active only one window

2008-10-03T02:51:15Z

One possible way to do log-in attached...

Vlad

Please access the attached hyperlink for an important electronic communications disclaimer: http://www.lse.ac.uk/collections/secretariat/legal/disclaimer.htm

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

login-example.rb (5K) Download Attachment

Re: Set active only one window

2008-10-02T11:25:41Z

You need to use a dialog box, or some other widget that runs modally. This will prevent interaction with any other windows.

From: fxruby-users-bounces@... [mailto:fxruby-users-bounces@...] On Behalf Of Soumyanath Chatterjee
Sent: Thursday, October 02, 2008 12:05 PM
To: fxruby-users@...
Subject: [fxruby-users] Set active only one window

Hi,

I am new to the world of FXRuby. Please bear with me if I ask a stupid question.

I am working on an application that requires user to login to use the software. Basically I wrote a simple code to create a second window that will ask for Login. After successful login the window is closed.

The problem is, user can click on the original window without compliting the login. I want the original window to be there but not accesseble till user has completed the login.

I could not find any clue in the documentation. Please help!

Regards

Soumya


This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Set active only one window

2008-10-02T11:05:04Z

Hi,

I am new to the world of FXRuby. Please bear with me if I ask a stupid question.

The problem is, user can click on the original window without compliting the login. I want the original window to be there but not accesseble till user has completed the login.

I could not find any clue in the documentation. Please help!

Regards

Soumya

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Re: Multiple feeds to one data target

2008-09-30T18:57:49Z

Lyle -

Bingo, you've got it.

On Tue, Sep 30, 2008 at 8:17 PM, Lyle Johnson <lyle@...> wrote:

On Sep 26, 2008, at 9:09 PM, Don Wilde wrote:

Please see extracted example in DATA following __END__. I'm constructing a tab page of a block of TextFields plus sliders in construct_slider, but I don't have the info-passing correct yet. I can trigger the puts with any SEL_COMMAND, but I'm not getting data back. I don't get the value from the #{@in_vals[ targ ].value }, nor do I get updated screen contents.

I've had to make some substitutions since the code you sent doesn't run (missing classes VMImage and VMImageFrame), but I think the main

Apologies. I stripped a lot more, should have left enough to let it run.

problem is that you never initialized the data target to any particular value. The main change I made was just to initialize it to 0.5 (arbitrarily picked):

@in_vals = {
:u_1 => FXDataTarget.new(0.5)
}

You bet, that did it. Thank you!!! :D

When I do this, both the text field and the slider start out with this value, and changing either the text field or slider value updates the data target's value as expected.

Hope this helps,

Lyle

---
"FXRuby: Create Lean and Mean GUIs with Ruby"
Now available from the Pragmatic Bookshelf!
http://www.pragprog.com/titles/fxruby

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Re: Multiple feeds to one data target

2008-09-30T18:12:55Z

On Sep 26, 2008, at 9:09 PM, Don Wilde wrote:

> Please see extracted example in DATA following __END__. I'm
> constructing a tab page of a block of TextFields plus sliders in
> construct_slider, but I don't have the info-passing correct yet. I
> can trigger the puts with any SEL_COMMAND, but I'm not getting data
> back. I don't get the value from the #{@in_vals[ targ ].value }, nor
> do I get updated screen contents.

I've had to make some substitutions since the code you sent doesn't
run (missing classes VMImage and VMImageFrame), but I think the main
problem is that you never initialized the data target to any
particular value. The main change I made was just to initialize it to
0.5 (arbitrarily picked):

@in_vals = {
:u_1 => FXDataTarget.new(0.5)
}

When I do this, both the text field and the slider start out with this
value, and changing either the text field or slider value updates the
data target's value as expected.

Hope this helps,

Lyle

---
"FXRuby: Create Lean and Mean GUIs with Ruby"
Now available from the Pragmatic Bookshelf!
http://www.pragprog.com/titles/fxruby

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Multiple feeds to one data target

2008-09-26T19:09:34Z

Hi, folks -

Having some amazing fun with FXRuby, but not getting all the way there despite Lyle's docs and book.

Please see extracted example in DATA following __END__. I'm constructing a tab page of a block of TextFields plus sliders in construct_slider, but I don't have the info-passing correct yet. I can trigger the puts with any SEL_COMMAND, but I'm not getting data back. I don't get the value from the #{@in_vals[ targ ].value }, nor do I get updated screen contents.

Please help an FXR noob get it right. All help appreciated!!!

-- Don

__END__

class VMDemoWindow < FXMainWindow

def initialize( app )

    image = VMImage.new( "wildebeest.jpg" )
    @in_vals = { :u_1     => FXDataTarget.new }
    super( app,
               "Statistics Tool",
                    :width => 550, :height => 450 )

    splitter = FXSplitter.new( self, :opts => SPLITTER_HORIZONTAL|LAYOUT_FILL )
    data_view = FXTabBook.new(splitter, :opts => LAYOUT_FILL )
    image_view = VMImageView.new( splitter, image )

    used_tab = FXTabItem.new( data_view, " % Used " )
    used_page = FXHorizontalFrame.new( data_view,
                                                        :opts => FRAME_RAISED | LAYOUT_FILL | PACK_UNIFORM_WIDTH )

    construct_used_page( used_page )

end

def construct_used_page( page )
    construct_slider( page, :u_1, "usage" )
end

def construct_slider( p, targ, str )

    s = FXVerticalFrame.new( p, :opts => FRAME_RAISED | LAYOUT_FILL )

    FXTextField.new( s, 3, :target => @in_vals[ targ ], :selector => FXDataTarget::ID_VALUE,
                            :opts => TEXTFIELD_NORMAL|LAYOUT_FILL_X ) do | t |
      t.justify = JUSTIFY_CENTER_X | JUSTIFY_CENTER_Y
      t.tipText = "Value for " + str
    end

    FXSlider.new( s, @in_vals[ targ ], :selector => FXDataTarget::ID_VALUE,
                       :opts => SLIDER_VERTICAL | SLIDER_TICKS_LEFT | LAYOUT_FILL ) do | aSlider |
      aSlider.range = Range.new( 1,.100 )
      aSlider.increment = 1
      aSlider.tickDelta = 10
      aSlider.tipText = "Value for " + str
      aSlider.height = 100
      aSlider.slotSize = 10
      aSlider.padTop = 10
      aSlider.padBottom = 10

    end

    @in_vals[ targ ].connect( SEL_COMMAND ) do | sender, sel, data |
      puts "\"#{ str }\" is now #{ @in_vals[ targ ].value }."
    end

end

end

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Re: FXTableItem.new segmentation fault

2008-09-25T13:50:36Z

The SWIG issue may indeed affect only versions of Ruby from 1.8.7 and
1.8.6 patchlevel 117 onward. I only saw the "object allocation during
garbage collection phase" message on Ruby 1.8.7. However, the
FXTableItem.new crash predates those versions. The backtrace I posted
was from ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-linux]. And I
have just now reproduced the crash on ruby 1.8.2 (2004-12-25)
[i386-mswin32].

As I observed in my last message, it looks like this crash happens when
garbage collection triggers a call to getIcon() during the
initialization of an FXTableItem, before the item is fully inserted into
FXRuby_Objects. This problem goes back to at least Ruby 1.8.2 and
FXRuby 1.6.14.

Tim Smith

-----Original Message-----
From: fxruby-users-bounces@...
[mailto:fxruby-users-bounces@...] On Behalf Of Lyle Johnson
Sent: Thursday, September 25, 2008 2:48 PM
To: fxruby-users@...
Subject: Re: [fxruby-users] FXTableItem.new segmentation fault

On Thu, Sep 25, 2008 at 1:00 PM, Melton, Ryan <rmelton@...> wrote:

> FXRuby does not work with Ruby 1.8.7 due to a bug in SWIG.
>
http://sourceforge.net/tracker/index.php?func=detail&aid=2034216&group_i
d=1645&atid=101645
>
> Unfortunately the same ruby change that results in the "object
allocation
> during garbage collection phase" made it into the Ruby 1.8.6 releases
as
> well at around version 117. So to use FXRuby, you must use a version
of
> Ruby 1.8.6 that is before r117.

I didn't realize that this "fix" also made it into Ruby 1.8.6.
Wonderful.

> Yes, this sucks. Hopefully SWIG will be fixed soon, or Lyle will work
> around the issue like the wxRuby group did.

I'll see what I can do.
_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users
_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Re: FXTableItem.new segmentation fault

2008-09-25T11:48:12Z

On Thu, Sep 25, 2008 at 1:00 PM, Melton, Ryan <rmelton@...> wrote:

> FXRuby does not work with Ruby 1.8.7 due to a bug in SWIG.
> http://sourceforge.net/tracker/index.php?func=detail&aid=2034216&group_id=1645&atid=101645
>
> Unfortunately the same ruby change that results in the "object allocation
> during garbage collection phase" made it into the Ruby 1.8.6 releases as
> well at around version 117. So to use FXRuby, you must use a version of
> Ruby 1.8.6 that is before r117.

I didn't realize that this "fix" also made it into Ruby 1.8.6. Wonderful.

> Yes, this sucks. Hopefully SWIG will be fixed soon, or Lyle will work
> around the issue like the wxRuby group did.

I'll see what I can do.
_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Re: FXTableItem.new segmentation fault

2008-09-25T11:00:02Z

FXRuby does not work with Ruby 1.8.7 due to a bug in SWIG. http://sourceforge.net/tracker/index.php?func=detail&aid=2034216&group_id=1645&atid=101645

Unfortunately the same ruby change that results in the “object allocation during garbage collection phase” made it into the Ruby 1.8.6 releases as well at around version 117. So to use FXRuby, you must use a version of Ruby 1.8.6 that is before r117.

Yes, this sucks. Hopefully SWIG will be fixed soon, or Lyle will work around the issue like the wxRuby group did.

Ryan

From: fxruby-users-bounces@... [mailto:fxruby-users-bounces@...] On Behalf Of Tim Smith
Sent: Thursday, September 25, 2008 11:44 AM
To: fxruby-users@...
Subject: Re: [fxruby-users] FXTableItem.new segmentation fault

I’ve had it crash with FXRuby 1.6.14 on XP, Vista, and Linux. I’ve also had it crash with ruby 1.8.7 on Linux, with the same failed assertion (FXRuby.cpp:1472), and the message “object allocation during garbage collection phase”. I’m including a tweaked version below which seems to crash more reliably within the first few minutes.

I’m also including a backtrace below. It appears that during the initialization of an FXTableItem, FXRbRegisterRubyObj() was called to associate the Ruby object with the Fox object in FXRuby_Objects. But while this was happening, garbage collection occurred, causing FXRbTableItem::markfunc() to be called, which called getIcon(), which led to a lookup in FXRuby_Objects for the Ruby object which was still in the process of being inserted there.

Tim Smith

require 'fox16'; include Fox

start = Time.now

count = 0

items = []

while true

10.times {|j|

items[j] = []

28125.times {|i|

items[j][i] = FXTableItem.new ''

}

count += 1

puts "#{count}, after #{Time.now - start} seconds"

end

FXRuby.cpp:1472: FXASSERT(!NIL_P(obj)) failed.

Breakpoint 1, rb_exc_raise (mesg=0) at eval.c:4616

4616 in eval.c

(gdb) bt

#0 rb_exc_raise (mesg=0) at eval.c:4616

#1 0x0805fb07 in rb_method_missing (argc=1, argv=0xfeefcff0, obj=4) at eval.c:5630

#2 0x0805c192 in rb_call0 (klass=4143832220, recv=4, id=3889, oid=4277134704, argc=1,

argv=0xfeefcff0, body=0xf6fdc130, flags=2) at eval.c:5702

#3 0x0805c70b in rb_call (klass=4143832220, recv=4, mid=3889, argc=1, argv=0xfeefcff0,

scope=1, self=6) at eval.c:6094

#4 0x0805cd4e in rb_funcall2 (recv=0, mid=3889, argc=1, argv=0xfeefcff0) at ruby.h:679

#5 0x0806008a in method_missing (obj=4, id=8311054, argc=0, argv=0x0,

call_status=-17832592) at eval.c:5671

#6 0x0805c744 in rb_call (klass=4143829940, recv=4, mid=32465, argc=0, argv=0x0, scope=1,

self=6) at eval.c:6090

#7 0x0805cfb6 in vafuncall (recv=4, mid=32465, n=0, ar=0xfeefd0f4) at ruby.h:679

#8 0x0805d0d2 in rb_funcall (recv=4277134704, mid=0, n=0) at eval.c:6188

#9 0xf6b274d7 in FXRbCallIconMethod (recv=0x9e511c0, func=32465) at FXRuby.cpp:1473

#10 0xf6b02dff in FXRbTableItem::getIcon (this=0x9e511c0) at impl.cpp:1011

#11 0xf6920945 in FXRbTableItem::markfunc (self=0x9e511c0) at markfuncs.cpp:517

#12 0x0806b672 in gc_mark_children (ptr=4129486760, lev=1) at gc.c:945

#13 0x0806bbca in mark_locations_array (x=0xfeefd9fc, n=5357) at gc.c:629

#14 0x0806be3e in garbage_collect () at gc.c:1368

#15 0x0806c7b2 in ruby_xmalloc (size=65708) at gc.c:103

#16 0x0806c96d in ruby_xcalloc (n=16427, size=65708) at gc.c:123

#17 0x080a9d35 in rehash (table=0x965ad78) at st.c:324

#18 0x080a9eb0 in st_insert (table=0x965ad78, key=166007232, value=166007264) at st.c:293

#19 0xf6b23c74 in FXRbRegisterRubyObj (rubyObj=4129486760, foxObj=0x9e511c0)

at FXRuby.cpp:253

#20 0xf69b71c7 in _wrap_new_FXTableItem (argc=3, argv=0xfeefe630, self=4129486760)

at table_wrap.cpp:846

#21 0x0805c192 in rb_call0 (klass=4143645140, recv=4129486760, id=73137, oid=4277134704,

argc=3, argv=0xfeefe630, body=0xf6fafc34, flags=2) at eval.c:5702

#22 0x0805c70b in rb_call (klass=4143645140, recv=4129486760, mid=73137, argc=3,

argv=0xfeefe630, scope=1, self=4129486760) at eval.c:6094

#23 0x08058773 in rb_eval (self=4129486760, n=0x0) at ruby.h:679

#24 0x08061bac in block_pass (self=4129486760, node=0xf635360c) at eval.c:8884

#25 0x08058d56 in rb_eval (self=4129486760, n=0x0) at eval.c:3189

#26 0x0805c06a in rb_call0 (klass=4143645140, recv=4129486760, id=2961, oid=4277134704,

argc=0, argv=0xfeeff8c4, body=0xf63546c4, flags=2) at eval.c:5998

#27 0x0805c70b in rb_call (klass=4143645140, recv=4129486760, mid=2961, argc=1,

argv=0xfeeff8c0, scope=1, self=6) at eval.c:6094

#28 0x0805ccfc in rb_funcall2 (recv=0, mid=2961, argc=1, argv=0xfeeff8c0) at ruby.h:679

#29 0x0805cd9a in rb_obj_call_init (obj=4129486760, argc=1, argv=0xfeeff8c0) at eval.c:7626

#30 0x0807f490 in rb_class_new_instance (argc=1, argv=0xfeeff8c0, klass=4143645140)

at object.c:1594

#31 0x0805c192 in rb_call0 (klass=4143832320, recv=4143645140, id=3353, oid=4277134704,

argc=1, argv=0xfeeff8c0, body=0xf6fdcacc, flags=0) at eval.c:5702

#32 0x0805c70b in rb_call (klass=4143832320, recv=4143645140, mid=3353, argc=1,

argv=0xfeeff8c0, scope=0, self=4143827360) at eval.c:6094

#33 0x08058773 in rb_eval (self=4143827360, n=0x0) at ruby.h:679

#34 0x08059eaa in rb_eval (self=4143827360, n=0x0) at eval.c:3450

#35 0x0805dfaf in rb_yield_0 (val=42379, self=4143827360, klass=0, flags=-152037876,

avalue=0) at eval.c:5021

#36 0x0805efca in rb_yield (val=4277134704) at eval.c:5105

#37 0x0807d64f in int_dotimes (num=56251) at numeric.c:2787

#38 0x0805c16e in rb_call0 (klass=4143813360, recv=56251, id=5473, oid=4277134704, argc=0,

argv=0x0, body=0xf6fd9228, flags=0) at eval.c:5702

#39 0x0805c70b in rb_call (klass=4143813360, recv=56251, mid=5473, argc=0, argv=0x0,

scope=0, self=4143827360) at eval.c:6094

#40 0x08058773 in rb_eval (self=4143827360, n=0x0) at ruby.h:679

#41 0x0805b3f7 in rb_eval (self=4143827360, n=0x0) at eval.c:3203

#42 0x0805dfaf in rb_yield_0 (val=3, self=4143827360, klass=0, flags=-152037596, avalue=0)

at eval.c:5021

#43 0x0805efca in rb_yield (val=4277134704) at eval.c:5105

#44 0x0807d64f in int_dotimes (num=21) at numeric.c:2787

#45 0x0805c16e in rb_call0 (klass=4143813360, recv=21, id=5473, oid=4277134704, argc=0,

argv=0x0, body=0xf6fd9228, flags=0) at eval.c:5702

#46 0x0805c70b in rb_call (klass=4143813360, recv=21, mid=5473, argc=0, argv=0x0, scope=0,

self=4143827360) at eval.c:6094

#47 0x08058773 in rb_eval (self=4143827360, n=0x0) at ruby.h:679

#48 0x0805b3f7 in rb_eval (self=4143827360, n=0x0) at eval.c:3203

#49 0x0805a152 in rb_eval (self=4143827360, n=0x0) at eval.c:3127

#50 0x0806369c in ruby_exec_internal () at eval.c:1634

#51 0x080636cc in ruby_exec () at eval.c:1654

#52 0x080645eb in ruby_run () at eval.c:1664

#53 0x08052888 in main (argc=2, argv=0xfef02e44, envp=0xfef02e50) at main.c:48

From: fxruby-users-bounces@... [mailto:fxruby-users-bounces@...] On Behalf Of Philippe Lang
Sent: Thursday, September 25, 2008 1:58 AM
To: fxruby-users@...
Subject: Re: [fxruby-users] FXTableItem.new segmentation fault

Maybe you should try with FXRuby 1.6.14?


This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Re: FXTableItem.new segmentation fault

2008-09-25T10:43:45Z

Tim Smith

require 'fox16'; include Fox

start = Time.now

count = 0

items = []

while true

10.times {|j|

items[j] = []

28125.times {|i|

items[j][i] = FXTableItem.new ''

}

count += 1

puts "#{count}, after #{Time.now - start} seconds"

end

FXRuby.cpp:1472: FXASSERT(!NIL_P(obj)) failed.

Breakpoint 1, rb_exc_raise (mesg=0) at eval.c:4616

4616 in eval.c

(gdb) bt

#0 rb_exc_raise (mesg=0) at eval.c:4616

#1 0x0805fb07 in rb_method_missing (argc=1, argv=0xfeefcff0, obj=4) at eval.c:5630

#2 0x0805c192 in rb_call0 (klass=4143832220, recv=4, id=3889, oid=4277134704, argc=1,

argv=0xfeefcff0, body=0xf6fdc130, flags=2) at eval.c:5702

#3 0x0805c70b in rb_call (klass=4143832220, recv=4, mid=3889, argc=1, argv=0xfeefcff0,

scope=1, self=6) at eval.c:6094

#4 0x0805cd4e in rb_funcall2 (recv=0, mid=3889, argc=1, argv=0xfeefcff0) at ruby.h:679

#5 0x0806008a in method_missing (obj=4, id=8311054, argc=0, argv=0x0,

call_status=-17832592) at eval.c:5671

#6 0x0805c744 in rb_call (klass=4143829940, recv=4, mid=32465, argc=0, argv=0x0, scope=1,

self=6) at eval.c:6090

#7 0x0805cfb6 in vafuncall (recv=4, mid=32465, n=0, ar=0xfeefd0f4) at ruby.h:679

#8 0x0805d0d2 in rb_funcall (recv=4277134704, mid=0, n=0) at eval.c:6188

#9 0xf6b274d7 in FXRbCallIconMethod (recv=0x9e511c0, func=32465) at FXRuby.cpp:1473

#10 0xf6b02dff in FXRbTableItem::getIcon (this=0x9e511c0) at impl.cpp:1011

#11 0xf6920945 in FXRbTableItem::markfunc (self=0x9e511c0) at markfuncs.cpp:517

#12 0x0806b672 in gc_mark_children (ptr=4129486760, lev=1) at gc.c:945

#13 0x0806bbca in mark_locations_array (x=0xfeefd9fc, n=5357) at gc.c:629

#14 0x0806be3e in garbage_collect () at gc.c:1368

#15 0x0806c7b2 in ruby_xmalloc (size=65708) at gc.c:103

#16 0x0806c96d in ruby_xcalloc (n=16427, size=65708) at gc.c:123

#17 0x080a9d35 in rehash (table=0x965ad78) at st.c:324

#18 0x080a9eb0 in st_insert (table=0x965ad78, key=166007232, value=166007264) at st.c:293

#19 0xf6b23c74 in FXRbRegisterRubyObj (rubyObj=4129486760, foxObj=0x9e511c0)

at FXRuby.cpp:253

#20 0xf69b71c7 in _wrap_new_FXTableItem (argc=3, argv=0xfeefe630, self=4129486760)

at table_wrap.cpp:846

#21 0x0805c192 in rb_call0 (klass=4143645140, recv=4129486760, id=73137, oid=4277134704,

argc=3, argv=0xfeefe630, body=0xf6fafc34, flags=2) at eval.c:5702

#22 0x0805c70b in rb_call (klass=4143645140, recv=4129486760, mid=73137, argc=3,

argv=0xfeefe630, scope=1, self=4129486760) at eval.c:6094

#23 0x08058773 in rb_eval (self=4129486760, n=0x0) at ruby.h:679

#24 0x08061bac in block_pass (self=4129486760, node=0xf635360c) at eval.c:8884

#25 0x08058d56 in rb_eval (self=4129486760, n=0x0) at eval.c:3189

#26 0x0805c06a in rb_call0 (klass=4143645140, recv=4129486760, id=2961, oid=4277134704,

argc=0, argv=0xfeeff8c4, body=0xf63546c4, flags=2) at eval.c:5998

#27 0x0805c70b in rb_call (klass=4143645140, recv=4129486760, mid=2961, argc=1,

argv=0xfeeff8c0, scope=1, self=6) at eval.c:6094

#28 0x0805ccfc in rb_funcall2 (recv=0, mid=2961, argc=1, argv=0xfeeff8c0) at ruby.h:679

#29 0x0805cd9a in rb_obj_call_init (obj=4129486760, argc=1, argv=0xfeeff8c0) at eval.c:7626

#30 0x0807f490 in rb_class_new_instance (argc=1, argv=0xfeeff8c0, klass=4143645140)

at object.c:1594

#31 0x0805c192 in rb_call0 (klass=4143832320, recv=4143645140, id=3353, oid=4277134704,

argc=1, argv=0xfeeff8c0, body=0xf6fdcacc, flags=0) at eval.c:5702

#32 0x0805c70b in rb_call (klass=4143832320, recv=4143645140, mid=3353, argc=1,

argv=0xfeeff8c0, scope=0, self=4143827360) at eval.c:6094

#33 0x08058773 in rb_eval (self=4143827360, n=0x0) at ruby.h:679

#34 0x08059eaa in rb_eval (self=4143827360, n=0x0) at eval.c:3450

#35 0x0805dfaf in rb_yield_0 (val=42379, self=4143827360, klass=0, flags=-152037876,

avalue=0) at eval.c:5021

#36 0x0805efca in rb_yield (val=4277134704) at eval.c:5105

#37 0x0807d64f in int_dotimes (num=56251) at numeric.c:2787

#38 0x0805c16e in rb_call0 (klass=4143813360, recv=56251, id=5473, oid=4277134704, argc=0,

argv=0x0, body=0xf6fd9228, flags=0) at eval.c:5702

#39 0x0805c70b in rb_call (klass=4143813360, recv=56251, mid=5473, argc=0, argv=0x0,

scope=0, self=4143827360) at eval.c:6094

#40 0x08058773 in rb_eval (self=4143827360, n=0x0) at ruby.h:679

#41 0x0805b3f7 in rb_eval (self=4143827360, n=0x0) at eval.c:3203

#42 0x0805dfaf in rb_yield_0 (val=3, self=4143827360, klass=0, flags=-152037596, avalue=0)

at eval.c:5021

#43 0x0805efca in rb_yield (val=4277134704) at eval.c:5105

#44 0x0807d64f in int_dotimes (num=21) at numeric.c:2787

#45 0x0805c16e in rb_call0 (klass=4143813360, recv=21, id=5473, oid=4277134704, argc=0,

argv=0x0, body=0xf6fd9228, flags=0) at eval.c:5702

#46 0x0805c70b in rb_call (klass=4143813360, recv=21, mid=5473, argc=0, argv=0x0, scope=0,

self=4143827360) at eval.c:6094

#47 0x08058773 in rb_eval (self=4143827360, n=0x0) at ruby.h:679

#48 0x0805b3f7 in rb_eval (self=4143827360, n=0x0) at eval.c:3203

#49 0x0805a152 in rb_eval (self=4143827360, n=0x0) at eval.c:3127

#50 0x0806369c in ruby_exec_internal () at eval.c:1634

#51 0x080636cc in ruby_exec () at eval.c:1654

#52 0x080645eb in ruby_run () at eval.c:1664

#53 0x08052888 in main (argc=2, argv=0xfef02e44, envp=0xfef02e50) at main.c:48

Maybe you should try with FXRuby 1.6.14?

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Re: FXTableItem.new segmentation fault

2008-09-25T00:55:20Z

Tim Smith wrote:

>
> Does the following code crash for anyone else? My app is unpredictably
> crashing with a segmentation fault, which I can sometimes reproduce
> with this contrived test case.
>
> require 'fox16'; include Fox
>
> start = Time.now
> count = 0
> items = []
> while true
> 28125.times {|i|
> items[i] = FXTableItem.new ''
> }
> count += 1
> puts "#{count}, after #{Time.now - start} seconds"
> end
>
> The eventual error:
>
> c:/program files/ruby/lib/ruby/gems/1.8/gems/fxruby-1.6.16-x86-mswin32-60/lib/fox16/kwargs.rb:2367: [BUG] Segmentation fault
> ruby 1.8.6 (2007-09-24) [i386-mswin32]
>
> I’ve had this code crash on XP and Vista (but not Linux), often in
> under a minute, though not always. Does anyone know what might be
> going on?
>
> Thanks for any help,
>

Hi Tim

It has been running for nearly an hour now on kernel
2.6.24.7-desktop-1mnb
with ruby 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]
fxruby 1.6.14
swapping cores at regular intervals, average cpu use 50%.
4 Gb RAM.
Count 4641 after 3680 seconds.

Len

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users

Re: FXTableItem.new segmentation fault

2008-09-24T22:57:48Z

Maybe you should try with FXRuby 1.6.14?

De : fxruby-users-bounces@... [mailto:fxruby-users-bounces@...] De la part de Tim Smith
Envoyé : jeudi, 25. septembre 2008 02:20
À : fxruby-users@...
Objet : Re: [fxruby-users] FXTableItem.new segmentation fault

It can be unpredictable. Sometimes it crashes if you just tweak it a bit, say by increasing the array size from 28125 to 281250, or creating multiple arrays.

Ive now had it crash on Linux, with ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-linux], and FXRuby 1.6.16. That error message is more detailed:

FXRuby.cpp:1472: FXASSERT(!NIL_P(obj)) failed.

/usr/local/lib/ruby/gems/1.8/gems/fxruby-1.6.16/lib/fox16/kwargs.rb:2367:in `old_initialize': undefined method `getIcon' for nil:NilClass (NoMethodError)

from /usr/local/lib/ruby/gems/1.8/gems/fxruby-1.6.16/lib/fox16/kwargs.rb:2367:in `initialize'

So it looks like in FXRuby.cpp, FXRbCallIconMethod() is calling FXRbGetRubyObj() and getting back nil?

Tim Smith

From: fxruby-users-bounces@... [mailto:fxruby-users-bounces@...] On Behalf Of Philippe Lang
Sent: Monday, September 22, 2008 3:10 AM
To: fxruby-users@...
Subject: Re: [fxruby-users] FXTableItem.new segmentation fault

Hi,

Your program is running just fine on my computer, for over 220 seconds now.

I'm using:

- Windows XP SP2

- ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]

- fxruby (1.6.14)

Philippe

De : fxruby-users-bounces@... [mailto:fxruby-users-bounces@...] De la part de Tim Smith
Envoyé : vendredi, 19. septembre 2008 22:32
À : fxruby-users@...
Objet : [fxruby-users] FXTableItem.new segmentation fault

Does the following code crash for anyone else? My app is unpredictably crashing with a segmentation fault, which I can sometimes reproduce with this contrived test case.

require 'fox16'; include Fox

start = Time.now

count = 0

items = []

while true

  28125.times {|i|

    items[i] = FXTableItem.new ''

  count += 1

  puts "#{count}, after #{Time.now - start} seconds"

end

The eventual error:

c:/program files/ruby/lib/ruby/gems/1.8/gems/fxruby-1.6.16-x86-mswin32-60/lib/fox16/kwargs.rb:2367: [BUG] Segmentation fault

ruby 1.8.6 (2007-09-24) [i386-mswin32]

Ive had this code crash on XP and Vista (but not Linux), often in under a minute, though not always. Does anyone know what might be going on?

Thanks for any help,

Tim Smith

_______________________________________________
fxruby-users mailing list
fxruby-users@...
http://rubyforge.org/mailman/listinfo/fxruby-users