This project is archived and is in readonly mode.
methods build with 'delegate' have a poor stack trace
Reported by Aaron Patterson | April 8th, 2010 @ 07:57 PM
Commit cd9ffd11 added lines to the method eval'd by "delegate". If an exception occurs in the eval'd method, the line numbers in the stack trace are confusing. The patch fixes it.
Comments and changes to this ticket
-
Aaron Patterson April 8th, 2010 @ 08:02 PM
- no changes were found...
-
Repository April 8th, 2010 @ 08:04 PM
- State changed from “new” to “resolved”
(from [0e44eb35d6e1b99ed624aaec839a03c12147f123]) fisting stack trace [#4349 state:resolved]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net
http://github.com/rails/rails/commit/0e44eb35d6e1b99ed624aaec839a03... -
af001 May 5th, 2011 @ 02:57 AM
- Importance changed from “” to “Low”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Aaron Patterson
Attachments
Tags
Referenced by
-
4349
methods build with 'delegate' have a poor stack trace
(from [0e44eb35d6e1b99ed624aaec839a03c12147f123])
fisting...