Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am an engineer on the Visual Studio Debugger team.</p> <p>Correct me if I am wrong, but it sounds like the only issue left is that when switching from PDBs to the .NET 4 dynamic compile symbol format some breakpoints are being missed.</p> <p>We would probably need a repro to exactly diagnose the issue, however here are some notes that might help.</p> <ol> <li>VS (2008+) can-to run as a non-admin</li> <li>Do any symbols load at all the second time around? You might test by breaking in (through exception or call System.Diagnostic.Debugger.Break())</li> <li>Assuming that symbols load, is there a repro that you could send us?</li> <li>The likely difference is that the symbol format for dynamic-compiled code is 100% different between .NET 2 (PDB stream) and .NET 4 (IL DB I think they called it?)</li> <li>The 'nop's sound about right. See rules for generating implicit sequence points below.</li> <li>You don't actually need to emit things on different lines. By default, VS will step 'symbol-statements' where, as the compiler writer you get to define what 'symbol-statement' means. So if you want each expression to be a separate thing in the symbol file, that will work just fine.</li> </ol> <p>The JIT creates an implicit sequence point based on the following rules: 1. IL nop instructions 2. IL stack empty points 3. The IL instruction immediately following a call instruction</p> <p>If it turns out we do need a repro to solve your issue, you can file a connect bug and upload files securely through that medium.</p> <p><strong>Update:</strong></p> <p>We are encouraging other users experiencing this issue to try the Developer Preview of Dev11 from <a href="http://www.microsoft.com/download/en/details.aspx?displaylang=en&amp;id=27543">http://www.microsoft.com/download/en/details.aspx?displaylang=en&amp;id=27543</a> and comment with any feedback. (Must target 4.5)</p> <p><strong>Update 2:</strong></p> <p>Leppie has verified the fix to work for him on the Beta version of Dev11 available at <a href="http://www.microsoft.com/visualstudio/11/en-us/downloads">http://www.microsoft.com/visualstudio/11/en-us/downloads</a> as noted in the connect bug <a href="https://connect.microsoft.com/VisualStudio/feedback/details/684089/">https://connect.microsoft.com/VisualStudio/feedback/details/684089/</a>.</p> <p>Thanks,</p> <p>Luke</p>
    singulars
    1. This table or related slice is empty.
    1. POMaking your .NET language step correctly in the debugger
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLuke
    1. USLuke
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks a lot. I will try make repro, if needed.
      singulars
      1. PO
      1. USleppie
    2. COAs for the confirmation, yes you are correct, but I would still prefer to solve the stepping issues without breaking verifiability. But as said, I am willing to sacrifice that if I could possibly prove that it will never throw a runtime `VerificationException`.
      singulars
      1. PO
      1. USleppie
    3. COAs for point 6, I simply made it 'line-based' for this question. The debugger does in fact step correctly in/out/over expressions like I intend it to work :) The only problem with approach is setting breakpoints on the 'inner' expressions if an 'outer' expression covers it; the debugger in VS tends to want to make the most outer expression as the breakpoint.
      singulars
      1. PO
      1. USleppie
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload