Re: [MacRuby-devel] [MacRuby] #343: 'IRB.conf[: MAIN_CONTEXT].to_s‘ crashes

#343: 'IRB.conf[:MAIN_CONTEXT].to_s‘ crashes +--- Reporter: d...@… | Owner: lsansone...@… Type: defect | Status: new Priority: major | Milestone: MacRuby 0.5

Re: [MacRuby-devel] How can I catch segment faults?

Hi, We will implement dwarf symbolication which will allow you to see the ruby method, filename and line instead of ?? in the gdb backtrace, but in the meantime an easy way to debug these problems is to toggle the ROXOR_VM_DEBUG variable to 1 in vm.cpp and recompile miniruby. This will pr

[MacRuby-devel] [MacRuby] #343: 'IRB.conf[: MAIN_CONTEXT].to_s‘ crashes

#343: 'IRB.conf[:MAIN_CONTEXT].to_s‘ crashes +--- Reporter: d...@… | Owner: lsansone...@… Type: defect | Status: new Priority: major | Milestone: MacRuby 0.5

Re: [MacRuby-devel] [MacRuby] #309: String, Hash, Array: singleton attr_accessor cannot be defined

#309: String, Hash, Array: singleton attr_accessor cannot be defined +--- Reporter: d...@… | Owner: lsansone...@… Type: defect | Status: new Priority: minor |

[MacRuby-devel] How can I catch segment faults?

Hey, after installing r2590 with backtrace support (thanks for that!) now I have the problem to catch segment faults. It seems to be a problem inside of a hash#each_pair, but I have absolutely no idea where, and because it is foreign code a file name and line number would be more than use

[MacRuby-devel] [MacRuby] #342: Wrong line numbers in backtrace

#342: Wrong line numbers in backtrace +--- Reporter: d...@… | Owner: lsansone...@… Type: defect | Status: new Priority: major | Milestone: MacRuby 0.5