#352: macirb does not eval UTF-String
+---
Reporter: d...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: major | Milestone: MacRuby 0.5
#352: macirb does not eval UTF-String
+---
Reporter: d...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: major | Milestone: MacRuby 0.5
#344: Segmentation fault: Hash and Array Inject
+---
Reporter: d...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: critical| Milestone: MacRuby 0
#344: Segmentation fault: Hash and Array Inject
+---
Reporter: d...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: critical|Milestone: MacRub
#352: macirb does not eval UTF-String
+---
Reporter: d...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: major | Milestone: MacRuby 0.5
I'm in the process of migrating an Objective-C project to MacRuby (0.5
trunk) and am seeing this error when I run the application:
*Assertion failed: (castIsValid(getOpcode(), S, Ty) && "Illegal SExt"),
function SExtInst, file Instructions.cpp, line 2508.*
*
*
The stack looks like this:
**
*
#353: No such file to load bigdecimal
--+-
Reporter: noelrap...@… | Owner: lsansone...@…
Type: defect| Status: new
Priority: blocker | Mi
Hi,
Do you run by any chance a 32-bit only machine? This could explain the
crash, the compiler has still 32-bit problems. This will be fixed in
the final 0.5 release.
Laurent
On Sep 27, 2009, at 2:27 PM, Art Taylor wrote:
I'm in the process of migrating an Objective-C project to MacRuby
It's a 64-bit machine (2008 8-core Mac Pro). I have a test machine I can
wipe and try it (pre-unibody 2008 mbp).
-a.
On Sun, Sep 27, 2009 at 2:33 PM, Laurent Sansonetti
wrote:
> Hi,
>
> Do you run by any chance a 32-bit only machine? This could explain the
> crash, the compiler has still 32-bit
I see. Could you check if your application is built for both 32-bit
and 64-bit? If it's for 32-bit only, then MacRuby will work in 32-bit
mode, which is bugged. You need to build it for 64-bit, this can be
configured in Xcode.
You can check with the file(1) command line tool if the binary
I've been running tests in 32-bit mode, and I can confirm that this is
definitely a 32-bit issue.
- Josh
On Sep 27, 2009, at 2:27 PM, Art Taylor wrote:
I'm in the process of migrating an Objective-C project to MacRuby
(0.5 trunk) and am seeing this error when I run the application:
Asser
Hi, I just did an svn update of the source and build problems do exist on
Snow Leopard. Did LLVM change ? Is there any way to add this dependency to
the overall build because I only had LLVM issues prior to my initial install
of it? Now, if LLVM revision starts changing without our knowledge, th
You hit it on the nose. I had specified x86_64 and 64-bit in the Project
settings, but for some reason it wasn't updating the project.pbxproj file in
the .xcodeproj. Manually updating the archs there did the trick.
Thanks!
-a.
On Sun, Sep 27, 2009 at 2:43 PM, Laurent Sansonetti
wrote:
> I see.
Hi Conrad
Yes the llvm revision changed. I generaly advertise it on the list but
I forgot this time. Sorry.
Check the README file for more info.
Laurent
Sent from my iPhone
On Sep 27, 2009, at 2:55 PM, Conrad Taylor wrote:
Hi, I just did an svn update of the source and build problems do
Hi Laurent, after rebuilding LLVM and MacRuby on Snow Leopard, I'm seeing
the following when I run 'macrake spec:ci':
$ macrake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-trunk)
unknown: warning: already initialized constant MACRUBY_VERSION
./mspec/bin/mspec ci -B ./spec/macruby.mspec
Hi Conrad,
This is well known, Matt worked on the specs yesterday night,
untagging specs that now pass, and apparently some of them should be
re-tagged :)
Stay tuned,
Laurent
On Sep 27, 2009, at 4:17 PM, Conrad Taylor wrote:
Hi Laurent, after rebuilding LLVM and MacRuby on Snow Leopard,
Laurent, thanks for the update. I just wanted to make sure that I'm in sync
with the current revision.
-Conrad
On Sun, Sep 27, 2009 at 4:43 PM, Laurent Sansonetti
wrote:
> Hi Conrad,
>
> This is well known, Matt worked on the specs yesterday night, untagging
> specs that now pass, and apparently
For some reasons, untagging some passing specs, broke other specs :p I'll be
investigating and untagging more specs. Expect to see some failures for a
few days.
Also, $ rake spec:ci:stats will give you more details about the specs
including the % passed per section.
- Matt
On Sun, Sep 27, 2009 a
18 matches
Mail list logo
