Trevor Norris 2cad7a69ce buffer: throw when writing beyond buffer ...

Previously one could write anywhere in a buffer pool if they accidently
got their offset wrong. Mainly because the cc level checks only test
against the parent slow buffer and not against the js object properties.
So now we check to make sure values won't go beyond bounds without
letting the dev know.

2013-05-20 15:23:23 -07:00

..

addons

test: modify async native test.js to test for #4820

2013-02-21 13:14:07 -08:00

disabled

Merge remote-tracking branch 'ry/v0.8' into master

2013-02-18 10:21:08 -08:00

fixtures

debugger: breakpoints in scripts not loaded yet

2013-05-02 08:52:58 +02:00

gc

test: use the debug build of node-weak when necessary

2012-06-13 17:58:28 -07:00

internet

DNS: Support NAPTR queries

2013-03-06 14:31:22 +04:00

message

process: separate nextTick domain logic

2013-02-27 16:37:10 -08:00

pummel

test: fix pummel/test-net-many-clients.js

2013-05-08 19:31:45 -07:00

simple

buffer: throw when writing beyond buffer

2013-05-20 15:23:23 -07:00

common.js

test: optionally set common.PORT via env variable

2013-03-02 19:09:39 +01:00