Not sure if that's the root cause (probably not) but why do you use hpricot
AND nokogiri? you also don't need the json gem since it's now packaged in
1.9.
Try not loading ruby-debugger19 and see if that's the problem.

- Matt

On Wed, Jul 20, 2011 at 10:29 AM, Ylan <[email protected]> wrote:

> Yeah, that didn't work:
>
> $rails s --debug
> ruby(910,0x7fff70a1acc0) malloc: *** error for object 0x100000000: pointer
> being freed was not allocated
> *** set a breakpoint in malloc_error_break to debug
> Abort trap
>
> Second time around:
>
> $rails s --debug
> => Booting WEBrick
> => Rails 3.0.9 application starting in development on http://0.0.0.0:3000
> => Call with -d to detach
> => Ctrl-C to shutdown server
> => Debugger enabled
> [2011-07-20 10:28:18] INFO  WEBrick 1.3.1
> [2011-07-20 10:28:18] INFO  ruby 1.9.2 (2011-07-09) [x86_64-darwin10.8.0]
> [2011-07-20 10:28:18] INFO  WEBrick::HTTPServer#start: pid=968 port=3000
>
> And I checked and I am using the brand new ruby with the brand new gemset:
>
> $ rvm info
>
> ruby-1.9.2-p290@locum:
>
> Really annoying!
>
> --
> Ylan
>
> --
> SD Ruby mailing list
> [email protected]
> http://groups.google.com/group/sdruby
>

-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to