On Nov 13, 10:02 am, Roger Pack <rogerpack2... / gmail.com> wrote:
> > I obviously can't speak for the OP, but I'd find a command-line option
> > to switch the console stack dump to full depth very handy.
>
> Amen.
> --
> Posted viahttp://www.ruby-forum.com/.

At the risk of appearing too doctrinaire, I think a command-line
option is not the right solution here. It should work correctly by
default. In the "production logs" use case I mentioned before, it is
very likely that the code that actually launches ruby is buried
somewhere deep in a system startup file, which means that we'd have to
patch all such files to pass in the "--backtraces-work-correctly" flag
on every system, which sounds like a logistical and political
nightmare.

So has anyone come up with answer to what is gained by omitting a
swath of callers in the middle of the trace?  Does anyone have a
reason why the current behavior is not incorrect?

 - A