On May 24, 2010, at 8:35 PM, Thibault Martin-Lagardette wrote:
> What is the test_mysql.rb file that you are running?
I don't think I'm doing any thread application or running test_mysql.rb at all.
I'm just running macrake in the mysql gem directory.
---
http://twitter.com/wagerlabs
_
It looks like rb_vm_dispatch is going into an infinite loop...
What is the test_mysql.rb file that you are running?
Also, with the exact same procedure, in lieu of doing "thread apply all bt",
could you try:
p (char *)sel
This is hoping the variable is not optimized away...
--
Thibault Martin-
On May 23, 2010, at 8:45 PM, Laurent Sansonetti wrote:
> Every time a program crashes, a crash log file is generated in
> ~/Library/Logs/CrashReporter (look for a macruby file there with the
> appropriate time stamp).
It's crashing in rb_vm_dispatch, e.g.
http://gist.github.com/411199
---
On May 23, 2010, at 12:38 PM, Joel Reymont wrote:
>
> On May 23, 2010, at 8:37 PM, Laurent Sansonetti wrote:
>
>> Do you have a gdb backtrace or a crash log handy?
>
> I don't know how to get one. I am just installing llvm and preparing to build
> macruby from source.
Every time a program cr
On May 23, 2010, at 8:37 PM, Laurent Sansonetti wrote:
> Do you have a gdb backtrace or a crash log handy?
I don't know how to get one. I am just installing llvm and preparing to build
macruby from source.
---
http://twitter.com/wagerlabs
___
MacRub
Hi Joel!
On May 23, 2010, at 12:01 PM, Joel Reymont wrote:
> Finally, I was able to narrow it down to a bug in macruby.
>
> I had to edit rbconfig.rb to remove "-arch i386" from ARCH_FLAG, leaving it
> with just "-arch x86_64" which works for me. Then I had to remove the
> compiled rbconfig.rb
Finally, I was able to narrow it down to a bug in macruby.
I had to edit rbconfig.rb to remove "-arch i386" from ARCH_FLAG, leaving it
with just "-arch x86_64" which works for me. Then I had to remove the compiled
rbconfig.rbo.
All of the above leaves me with the bus error below. How do I debu
Narrowing this down further, the issue seems to be with CFLAGS generated by
mkmf, e.g.
macirb
require 'mkmf'
create_makefile 'test'
This puts both '-arch i386' and '-arch x86_64' into CFLAGS.
Any suggestions on how to control the architectures that mkmf puts in CFLAGS?
ARCHFLAGS="-arch x86_6
I was able to advance with the mysql gem but somehow '-arch i386' is making its
way into my build pipeline, despite building for x86_64. extconf.rb seems to
store the wrong flags into the Makefile.
Any suggestions how to fix this?
Thanks, Joel
---
biggie:mysql-gem joelr$ ARCHFLAGS="-a
On May 23, 2010, at 9:19 AM, Laurent Sansonetti wrote:
> What's happening exactly? What problem do you see? I assume there is a
> gemspec file in the project with a makefile or rakefile task to generate the
> gem.
The problem was due to a missing ~/.rubyforge/user-config.yml which 'rubyforge
On May 23, 2010, at 1:10 AM, Joel Reymont wrote:
>
> On May 23, 2010, at 9:02 AM, Laurent Sansonetti wrote:
>
>> Feel free to file a ticket if you want to track that issue.
>
> https://www.macruby.org/trac/ticket/728
Thanks :)
>> In the meantime I'm afraid you will have to change the code man
On May 23, 2010, at 9:02 AM, Laurent Sansonetti wrote:
> In the meantime I'm afraid you will have to change the code manually, as you
> already did...
I can't manage to do this: http://pastie.org/973144
Thanks, Joel
---
http://twitter.com/wagerlabs
___
On May 23, 2010, at 9:02 AM, Laurent Sansonetti wrote:
> Feel free to file a ticket if you want to track that issue.
https://www.macruby.org/trac/ticket/728
> In the meantime I'm afraid you will have to change the code manually, as you
> already did...
My problem is that I can't manage to ins
Hi Joel,
Indeed, we noticed that problem too. The plan for 0.7 is to clean out our
public headers so that the true symbol is no longer pre-defined. Feel free to
file a ticket if you want to track that issue.
In the meantime I'm afraid you will have to change the code manually, as you
already d
mysql-gem does not install with mysql-5.1.47 because ext/mysql_api/mysql.c:878
has this code:
my_bool true = 1;
Unfortunately, 'true' is defined as 1 so you end up with
my_bool 1 = 1;
which is an error.
I fixed the issue in my local mysql-gem directory but for the life of me
15 matches
Mail list logo