David Kleiner wrote: > I went through several rounds of pain to get webstack going. Now I have 2 > ruby environments, the 1.8.7 from Sunfreeware and my own, /opt/webstack/ruby > stuff. The /usr/local/bin/ruby (Joyent uses pkgsrc) is running 7 production > mongrels, and /opt/webstack/bin/ruby, which is > > [admin at fhgyztbq ~]$ /opt/webstack/bin/ruby -v > ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-solaris2.10] > > running a single mongrel that I am trying to debug. > > I am trying to find out the origin of memory explosion with this app and > going through a crash course in dtrace. Are there any additional dtrace > ruby-specific scripts you guys have? > > Thank you! > > /David >
Pretty much everything that we use is in the DTraceToolkit: http://opensolaris.org/os/community/dtrace/dtracetoolkit/ The ld problem you have is caused by unknown flags being passed to the linker (ld). The fix is to modify the LDSHARED value in /opt/webstack/ruby/1.8/lib/ruby/1.8/i386-solaris2.11/rbconfig.rb It will currently be something like: CONFIG["LDSHARED"] = "ld -G" and you need to change it so that it calls gcc (which itself calls ld). Assuming that CC is set in rbconfig.rb you could set it to: CONFIG["LDSHARED"] = "$(CC) -G" or you could hard code the path to gcc in place of $(CC) Amanda
