[Mono-bugs] [Bug 387506] Usability: stack traces do not include parameter names

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed May 7 02:47:04 EDT 2008


User martin at novell.com added comment

Martin Baulig <martin at novell.com> changed:

           What    |Removed                                         |Added
             Status|NEW                                             |RESOLVED
         Resolution|                                                |FEATURE

--- Comment #1 from Martin Baulig <martin at novell.com>  2008-05-07 00:47:03 MST ---
Good point, but this is a feature not a bug.

Just use `up' and `down' to move through the frames and then do `show params'
(for parameters) and `show locals' (for locals).

There are two primary reasons why this isn't included in a backtrace:

a) One key objective for the debugger is to have the backtrace code as
   robust as it possibly could be.  Printing parameters in other stack frames
   should work most of the time, but there are a lot of things which may go
   wrong, for instance they may be stored in registers which aren't valid
   anymore etc.

b) Printing parameters is mostly useless without doing method invocations;
   most managed types have a custom ToString(), but use mainly properties
   and not fields for their publicly visible data.

Support could probably be added for simple types, but it'd just confuse that
user if we only do simple types and no structs/classes/arrays etc.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list