Commit Graph

11 Commits

Author SHA1 Message Date
~hatteb-mitlyd
e2bf68ab7e Revert "Revert "use nash for cue""
This reverts commit 04caeff12f5e471519082b1c5f3020943df136db.

Medical science made some advances by leaps and bounds. The nash code is
more aggressive with the allocator and leaves more garbage around for
e.g. u2_term_io_init to trip over.
2014-04-30 11:34:43 -07:00
~hatteb-mitlyd
2c93a4efff Revert "use nash for cue"
This reverts commit f691d25bd23716e9411288d3eb9bd4c9b9d33ae1.

Oddly, this causes a failure to boot, on some linux, for some reason
heretofore unknown to medical science.
2014-04-30 11:15:45 -07:00
~hatteb-mitlyd
61c0a6ed2c use nash for cue 2014-04-29 10:03:31 -07:00
~hatteb-mitlyd
a0c18f56b2 change to asserting malloc 2014-04-01 17:48:26 -07:00
C. Guy Yarvin
98006a2851 Last checkin on funbreach. 2014-01-06 12:37:42 -08:00
Steven Dee
f2a839426b Ye olde whitespace cleanup part 2
sed -i, glanced at.
2013-12-18 13:17:47 -08:00
C. Guy Yarvin
a4baea40fd Fix a bunch of memory leaks and stuff. 2013-11-11 23:09:11 -08:00
Steven Dee
324c6a235d Remove most instances of strcpy and sprintf
OpenBSD whines about these and recommends using strlcpy / snprintf
instead. Since strlcpy isn't quite universal yet, we use strncpy instead
and be careful about terminating the string. We could implement a
portable strlcpy in terms of strncpy, but that'd add another function to
the namespace.

Yes, usually the length is obviously bounded. Still, pretending
strcpy/sprintf don't exist seems like a great strategy.

N.B. there are still a few occurrences of strcpy and sprintf under f/
and in libuv, but I don't have time to tackle them right now.
2013-10-30 15:25:22 -04:00
Steven Dee
1a6f18d09d Consider both FreeBSD and OpenBSD "bsd" 2013-10-07 12:31:41 -04:00
Lev Serebryakov
018cfe5eaf Quick'n'dirty port to FreeBSD (checked on FreeBSD 9.2/amd64) 2013-10-02 18:44:22 +04:00
Christian Carter
3af3130bdc Cleaning up old code 2013-09-28 13:21:18 -07:00