[ ruby-Bugs-4151 ] Stack trace doesn't include class

Bugs item #4151, was opened at 2006-04-17 23:10
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=4151&group_id=426

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Oren Ben-Kiki (oren)
Assigned to: Nobody (None)
Summary: Stack trace doesn't include class

Initial Comment:
The stack trace provided by the Ruby engine uses a hard-wired template including the source file name, line number and the name of the method. For some reason, it doesn't contain the name of the class containing the method.

A lot of Ruby functionality is provided as extensions to the standard library, where it makes sense to have one file per class (more or less). This compensates for the above lack to a great extent.

However, it also makes sense to write straight scripts in Ruby. In my case, quite an involved script that contains many classes, but is still a single file I can easily distribute to users etc. In this case, the lack of the class name in the stack trace is rather limiting.

Since many people depend on the current hard-wired format of the stack trace, it doesn't make sense to simply upgrade it to contain the class name. Such an extension would have to be triggered by a flag to the ruby interpreter.

It seems that if such a flag was added, it would make sense to allow it to provide a replacement template for the stack trace line, and provide as many fields to be used in it (such as class, time, memory usage, ...).

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=4151&group_id=426