dotgnu-pnet
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pnet-developers] [bugs #9151] (new StackFrame(1, true)).GetFileName() s


From: Gopal.V
Subject: [Pnet-developers] [bugs #9151] (new StackFrame(1, true)).GetFileName() sometimes returns null when it shouldn't
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

This mail is an automated notification from the bugs tracker
 of the project: DotGNU Portable.NET.

/**************************************************************************/
[bugs #9151] Latest Modifications:

Changes by: 
                Gopal.V <address@hidden>
'Date: 
                Sat 05/29/2004 at 14:40 (Asia/Calcutta)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
Fixed in CVS 29th May 2004 (didn't make it into 0.6.6)

The problem was when the native offset matched the last debug marker ... now it 
checks for the "==" case as well as ">" case.






/**************************************************************************/
[bugs #9151] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9151>
Project: DotGNU Portable.NET
Submitted by: Richard Baumann
On: Fri 05/28/2004 at 23:55

Category:  None
Severity:  5 - Average
Item Group:  None
Resolution:  Fixed
Assigned to:  None
Status:  Closed


Summary:  (new StackFrame(1, true)).GetFileName() sometimes returns null when 
it shouldn't

Original Submission:  Creating a stack frame for the previous method in the 
call stack does not always produce a valid stack frame for that method. The 
GetFileName method sometimes returns null when it shouldn't. It appears to be a 
problem with the offset calculations, because increasing the amount of code in 
the previous method can cause the stack frame for that method to work 
correctly. I've attached a test case which has blocks of code which can be 
defined in to show how the behavior changes. There's a comment at the beginning 
of the test case class explaining what each define does.

P.S. Remember to compile with -g.

Follow-up Comments
------------------


-------------------------------------------------------
Date: Sat 05/29/2004 at 14:40       By: t3rmin4t0r
Fixed in CVS 29th May 2004 (didn't make it into 0.6.6)

The problem was when the native offset matched the last debug marker ... now it 
checks for the "==" case as well as ">" case.






File Attachments
-------------------

-------------------------------------------------------
Date: Fri 05/28/2004 at 23:55  Name: stack-frame-test-case.cs  Size: 1KB   By: 
Rich333
Test case showing the problem.
http://savannah.gnu.org/bugs/download.php?item_id=9151&amp;item_file_id=1354






For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=9151>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]