Somewhat related when trying to improve performance is doing debugging of
how long operations take.
Puppet already makes some use of this, but it's worth noting that for a
given section of code, you can use the existing Benchmark code to do this.
ie you can surround a code block with something li
On Mon, 2008-09-08 at 10:39 -0600, Andrew Shafer wrote:
>
> I've been using a combination of GDB, DTrace, puts caller and puts
> 'WTF'
>
> GDB can be like staring into the abyss.
>
> DTrace seems the most powerful and promising, but a bit of a learning
> curve.
>
> puts is primitive, but it wo
Nigel Kersten wrote:
> so I've found myself with a few reasons to need to debug
> puppetd/puppetmasterd lately since we upgraded to 0.24.5
>
> I've been doing this by basically throwing Puppet.notice/warning
> statements into the code, which feels rather primitive...
>
> How are people doing deb
I've been using a combination of GDB, DTrace, puts caller and puts 'WTF'
GDB can be like staring into the abyss.
DTrace seems the most powerful and promising, but a bit of a learning curve.
puts is primitive, but it works.
Would love to swap tips and tricks with anyone debugging Ruby in general
