Index

Show enters and exits. Hide enters and exits.

03:40:29brixenevan: do it! :)
03:57:05matthewdSo, there are actually a number of classes that shouldn't be able to be explicitly created: Fixnum, Bignum, NilClass...
04:00:42matthewdJust undef_method(:new) and override allocate to raise a TypeError? Or is this something Class#allocate should intrinsically understand and enforce?
04:05:56brixenClass#allocate, no
04:07:26matthewdOkay, do we don't care about the VM crashing if someone does something crazy from ruby-land?
04:07:36matthewd(involving re-binding methods, etc)
04:07:47brixenI would be inclined to make .allocate per class raise
04:07:57brixenor add a mixin like we have for ImmediateValue
04:08:18brixenwhat do you mean by VM crash?
04:08:37brixenthe vm should never segfault
04:08:52brixenbut I don't care about raising terrible exceptions when user's do stupid shit
04:08:59brixen-'
04:09:13matthewdIf you Class.instance_method(:allocate).bind(Bignum).call, you end up with an uninitialized Bignum, which will then get past all our other type checks
04:09:28brixenhuh?
04:09:43brixenwhat do you mean by other type checks?
04:10:19matthewdas<Bignum>()-type stuff... or at least, my reading suggests it'd get past that
04:10:45brixenwell, this segfault should not happen
04:10:50brixenfile a ticket on that
04:10:59brixeneven though that code is stupid as fock
04:11:03matthewdSee, eg, the infinite loop right now for `Fixnum.new + 1`
04:11:11brixenwe need to address it in a way that does not segfault
04:11:40brixenyeah, file a ticket, let's see how evan wants to address it
04:11:51brixenI'm doing "other than rbx" stuff atm :)
04:12:20evanFixnum.new should not work.
04:12:24evanif it does, thats a bug.
04:12:30evanalso
04:12:30matthewdevan: Right
04:12:39evanare you just trying terrible things?
04:12:42evanor did you see this in real code?
04:12:57evanthat info is important when you open the issue
04:13:01evanwhich you should do now.
04:13:03matthewdI did a Bignum.new accidentally while experimenting
04:13:32evani'm thinking about instituting new punishments for people who sit on bugs and don't open issues
04:13:33evan:)
04:13:38matthewdYeah, I was just trying to work out what the issue is
04:15:25evanmatthewd: i'd prefer you open the issue with the problem
04:15:30evanand if you explore it more and find more out
04:15:33evanleave a comment on it.
04:15:59evani can pretty plainly see whats going on
04:16:09evani'm not sure what more you're looking for
04:16:20dkubbevan: heh, I'm the same way. saw some failures in one project's specs, but since I haven't isolated the prob I didn't want to bother anyone
04:16:41evanif it's a clean repro
04:16:46evanopen the issue.
04:16:50matthewdClearly we need to kill Bignum.allocate and Bignum.new
04:16:53evanthats generally the rule.
04:17:11evanif you want to explore what is happening in the repro, fine too
04:17:22evanbut don't sit on a clean repro'd bug for any reason.
04:17:29dkubbyeah, it's not reprod yet. just some specs that fail with rbx and not with other rubies
04:17:56evanok, sure.
04:18:28evanbut if there is no issue, then don't complain that it's not fixed :)
04:18:43dkubbof course :)
04:19:57matthewdevan: But do we want to protect against Class#allocate being being rebound, and thus tricked into creating an instance of a "special" class, which other parts of the VM will later assume to be initialized in a particular way, etc.
04:20:11evanmatthewd: we have to.
04:20:22evanno ruby code is allowed to crash the VM.
04:20:30matthewdYeah, that's what I suspected
04:20:35evanperiod.
04:20:47evanyou're issue only mentions Bignum.new
04:20:50evanwhat about Fixnum.new?
04:20:54matthewdSo, we'll need to give the VM an intrinsic understanding that certain classes can't be allocated
04:20:54evanare you openning that as another issue?
04:21:34evanwell, perhaps.
04:21:39evani'll need to think about it.
04:21:51evanbut not on a saturday night.
04:21:56evan:)
04:25:33matthewdevan: Commented
09:10:11radarekwhen I try to build from master i get "make: *** No rule to make target `ruby.h', needed by `openssl_missing.o'. Stop."
09:10:13radarekany idea?
09:14:01matthewdradarek: Try a `rake clean`
09:57:58radarekmatthewd: thanks, it's ok now
11:06:14asymmetrichi guys
11:06:22asymmetrici have a patch that i'd like to submit
11:06:30asymmetrichow should i proceed?
11:07:13somebodyasymmetric, creates a ticket
11:08:43asymmetricon github?
11:09:14somebodyyep
11:18:34asymmetrichow do i add labels to issues?
11:19:04asymmetricanyway, the issue is here http://github.com/evanphx/rubinius/issues/issue/336
11:22:40dbussinkasymmetric: did you hit this with something? curious as to what would supply both options
11:23:29asymmetricwell, it actually seemed quite illogical that if i specify both (by mistake), --disble takes precedence, no matter the order
11:52:04somebodyasymmetric, Only contributers can add labels
11:54:43asymmetricsomebody_: k, thanks
22:25:42vladsharpis kconv not available on rubinius
22:25:43vladsharp?