Home Dashboard Directory Help
Search

VC++ 2010 Line Number Wrapping by RPBurkholder


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 632850
Opened: 12/21/2010 1:22:05 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

When compiling the amalgamated sqlite3.c from www.sqlite.org, the file is over 100,000 lines long. When tracing into the file, the wrong line number is found. For example, tracing to openDatabase is actual line 106372, but the debugger thinks it is 40840, which is a difference of 65532, which indicates almost a 16 bit line counter wrap. Because of the wrap, the debugger brings up the source file, but goes to the incorrect line number. And gets totally confused.

Is there a way to get around this for the time being?
Details
Sign in to post a comment.
Posted by RHampshire1953 on 4/6/2012 at 9:56 AM
Hi,

I am having the problem with VC++ that when the line counter exceeds 65535 it wraps back to 0. I have done a windows update get all the latest updates. My Visual Studio info is:

Microsoft Visual Studio 2010
Version 10.0.40219.1 SP1Rel

If you could help me get the fix reported below I would appreciate it.


Posted by Microsoft on 1/28/2011 at 2:24 PM
Hi,

Thank you for reporting this bug. We've fixed in latest build and you should get the fix in our next deliverable.

Best regards,
Smile Wei
VC++ FE Team
Posted by Microsoft on 12/22/2010 at 10:37 PM
Thank you for attaching the sample project to help us reproduce this issue. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.These specialized experts will follow-up with your issue.
Posted by RPBurkholder on 12/22/2010 at 7:07 AM
Can you recommend a video capture ap to use?

In the meantime, I have attached a sample project. Compiile and step into sqlite3_open_v2. You'll find you end up on line 41098 in sqlite3.c. But if you do a symbol search for sqlite3_open_v2 in sqlite3.c, you should actually be on line 106630. It appears that the debugger is resolving unsigned 16 bit line numbers rather than 32 bit line numbers.

Does that help?
Posted by Microsoft on 12/22/2010 at 1:25 AM
Thank you for reporting this issue.
Could you please attach a video to help us better understand this scenario?
Posted by Microsoft on 12/21/2010 at 2:23 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
sqltest4ms.zip (restricted) 12/22/2010 -