Sorry, I don't know if I missed something or not.
Currently MacRuby has a GC (as does Ruby) and it is based on Obj-C's
GC. This means that code pulled in to MacRuby MUST be GC currently.
In my opinion this isn't horrible or extremely difficult as you can
compile frameworks as -fobjc-gc inst
Very hard to tell, sorry. Contact me offline with a copy of your app
and I can investigate (if you don't want to share your source code
here).
Laurent
On Sep 23, 2009, at 5:57 PM, Robert Rice wrote:
Hi again:
Does this help?
(gdb) bt
#0 0x7fff827521b2 in +[NSThread callStackSymbols]
Hi again:
Does this help?
(gdb) bt
#0 0x7fff827521b2 in +[NSThread callStackSymbols] ()
#1 0x00010213700c in ?? ()
#2 0x000102132034 in ?? ()
#3 0x7fff81ab7408 in -[NSIBObjectData instantiateObject:] ()
#4 0x7fff81ab67f2 in -[NSIBObjectData
nibInstantiateWithOwner:topL
Hi Robert,
This one will be hard to debug without your code. At least, from gdb,
could you do a "bt" and copy/paste the output?
Laurent
On Sep 23, 2009, at 5:17 PM, Robert Rice wrote:
Hi Laurent:
Thanks again. This gets me past the compile crashes but now the
execution doesn't get very
Hi Laurent:
Thanks again. This gets me past the compile crashes but now the
execution doesn't get very far before I get “EXC_BAD_INSTRUCTION” with
no backtrace. Any suggestions?
Program loaded.
run
[Switching to process 1521]
Running…
rb_main
requiring AppDelegate.rb
requiring DataBaseNew.r
In regards to a MacRuby application, you would need to use GC for
Objective-C.
-Conrad
On Wed, Sep 23, 2009 at 5:00 PM, Jordan Breeding wrote:
> But would the new MacRuby interpreter be smart enough to switch between
> them and prefer GC Objc-C code, or would it be locked to one or the other?
>
But would the new MacRuby interpreter be smart enough to switch
between them and prefer GC Objc-C code, or would it be locked to one
or the other?
Sent from my iPhone
On Sep 23, 2009, at 18:56, Conrad Taylor wrote:
Hi, Objective-C could use GC and non-GC for memory management on the
desk
Hi, Objective-C could use GC and non-GC for memory management on the
desktop.
-Conrad
On Wed, Sep 23, 2009 at 4:51 PM, Jordan Breeding wrote:
> So in that case Ruby would be garbage collected, but ObjC code it uses will
> be ref counted?
>
> Sent from my iPhone
>
>
> On Sep 23, 2009, at 18:00, La
So in that case Ruby would be garbage collected, but ObjC code it uses
will be ref counted?
Sent from my iPhone
On Sep 23, 2009, at 18:00, Laurent Sansonetti
wrote:
Hi Conrad,
The thing is, MacRuby is built on top of the ObjC GC, so there is
currently no way you can not use it :)
In
Hi Conrad,
The thing is, MacRuby is built on top of the ObjC GC, so there is
currently no way you can not use it :)
In the future we might introduce a mode where MacRuby doesn't use this
GC, but it's all tentative.
Laurent
On Sep 23, 2009, at 3:58 PM, Conrad Taylor wrote:
Laurent, I und
Laurent, I understand that one should use the GC for MacRuby but why do we
have such a restriction? Just curious about the history here.
Thanks in advance,
-Conrad
On Wed, Sep 23, 2009 at 3:49 PM, Laurent Sansonetti
wrote:
> Hi Robert,
>
> The problem here is dealloc. Same reason, dealloc is ig
Hi Robert,
The problem here is dealloc. Same reason, dealloc is ignored by the
runtime, and you should not use it in MacRuby, it will never be called.
I just fixed macruby to not crash in case autorelease or dealloc is
used, but keep in mind that using these selectors won't do anything.
L
Hi, is this the complete application? If not, could you generate subset of
your application that can be ran which produces the error message?
-Conrad
On Wed, Sep 23, 2009 at 2:46 PM, Robert Rice wrote:
> Hi Laurent:
>
> Thanks for your quick reply. I have attached another file that causes a
> s
Hi Laurent:
Thanks for your quick reply. I have attached another file that causes
a similar crash without a call to autorelease.
Bob Rice
#
# OutlineRowNode.rb
# Cocoa-Ruby Driver Assistant
#
# Created by Robert Rice on 9/4/09.
# Copyright (c) 2009 Rice Audio. All rights reserved.
#
requ
Hi Robert,
The problem is line 68, the call to autorelease. If you remove it it
should load again. The reason is that autorelease (like release and
retain) are ignored selectors of the runtime. Clearly we should not
crash this way, I will fix that.
Also, keep in mind that retain, release
Hi Laurent:
Thanks for your offer to help. Sorry I was busy with another project
but now I get back to MacRuby.
I have attached a file that causes the assertion error when loaded by
the require command. Probably there is something else I need to change
when porting from Ruby-Cocoa.
Than
Hey Conrad,
The readme that should get you started with the specs is available in
spec/README.rdoc (http://github.com/masterkain/macruby/blob/master/spec/README.rdoc
).
I'm sure there will be some issues you run into as I haven't updated
it in a while. Feel free to update it and/or ask me qu
Actually it's a bit more complicated than that since we need to tag
specs before adding them to rake spec:ci
I'm sure Eloy will explain where to find the spec readme and conventions
Sent from my iPhone
On Sep 16, 2009, at 13:54, Conrad Taylor wrote:
Hi Matt, thanks for gettih back to me. I
Hi Matt, thanks for gettih back to me. In regards to the failing
specs, how does one determine what's failing? I have been running the
following:
rake spec:ci
In any case, I would like to get started on this as soon as possible.
Thus, if someone can provide the details, it would be grea
Unfortunately, we don't have a check list of all the std libs and other gems
that are compatible/incompatible.
The todo list mentions the following:
Planned for 0.5
[ ] fix irb Binding bugs
[/] sockets
[ ] backtracing / symbolication
[/] rubygems should work (modulo C extensions)
[X] fix versio
Is there a page where can locate what's not working? Or open projects that
need help? I would be interested in both erb and the webserver (i.e.
webrick, mongrel, and/or thin)?
Thanks in advance,
-Conrad
On Tue, Sep 15, 2009 at 4:02 PM, Matt Aimonetti wrote:
> You should always use macgem when
You should always use macgem when working with macruby.
However, Sinatra isn't running yet as erb isn't fully working neither rack
and we don't have a compatible webserver ;)
You will have to wait a little before that works, but as we are going
through the std libs, things should start looking bet
On Thu, Sep 10, 2009 at 11:24 AM, Matt Aimonetti wrote:
> Latest trunk code available as an unofficial pkg ready to install:
> http://rubyurl.com/5K3W
>
> Lots of bug fixes, improved macgem (not finished yet but you can install
> gems and load them using `gem 'gem_name'; require 'whatever'`).
> Th
Hi Robert,
Unless you found what was wrong, feel free to contact me off-list with
a copy of your app and I will investigate the problem.
Laurent
On Sep 12, 2009, at 9:48 AM, Robert Rice wrote:
Hi Laurent:
It's a relatively large application that I ported from a RubyCocoa
environment.
I
Hi Laurent:
It's a relatively large application that I ported from a RubyCocoa
environment.
I need the threading support hook that was removed from Ruby in the
Snow Leopard release.
I'll try to track it down better by porting and testing modules a
little at a time.
Thanks,
Bob Rice
On
Looks like we are hitting an assertion in the symbol generator...
Could you send us what you are trying to execute here?
Laurent
Sent from my iPhone
On Sep 11, 2009, at 9:48 AM, Robert Rice wrote:
How would I track down the following error from the nightly build?
[Session started at 2009-
How would I track down the following error from the nightly build?
[Session started at 2009-09-11 12:43:22 -0400.]
GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul 3 01:19:56
UTC 2009)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Publ
Latest trunk code available as an unofficial pkg ready to install:
http://rubyurl.com/5K3W
Lots of bug fixes, improved macgem (not finished yet but you can install
gems and load them using `gem 'gem_name'; require 'whatever'`).
Things are looking pretty good on trunk :)
- Matt
___
28 matches
Mail list logo
