Boo

BooBinding crashes most of #develop.

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 0.7.5
  • Component/s: None
  • Labels:
    None
  • Environment:
    svn 595
  • Number of attachments :
    0

Description

Steps to reproduce:

Create new Boo winforms project.

Set debugging breakpoints.

Run project.

Close running application.

#develop "crashes" - several panes vanish and #dev throws an exception when you try to exit by clicking on big red X.

Too many exceptions to cut and paste here.

Issue Links

This issue depends upon:
BOO-527 Make .pdb files work under .NET 1.1 and .NET 2.0 Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Daniel Grunwald added a comment -

The debugger goes crazy when it doesn't find the debugger symbols like expected.

Show
Daniel Grunwald added a comment - The debugger goes crazy when it doesn't find the debugger symbols like expected.
Hide
Permalink
Arron Washington added a comment -

Does this mean there's something wrong with the .pdb that Boo generates, or is it a general #dev bug?

Show
Arron Washington added a comment - Does this mean there's something wrong with the .pdb that Boo generates, or is it a general #dev bug?
Hide
Permalink
Daniel Grunwald added a comment -

Both. The SharpDevelop debugger won't work with the .pdb files (the only location where a breakpoint works is on a "for" loop), but it shouldn't totally crash.

Show
Daniel Grunwald added a comment - Both. The SharpDevelop debugger won't work with the .pdb files (the only location where a breakpoint works is on a "for" loop), but it shouldn't totally crash.
Hide
Permalink
Arron Washington added a comment -

I can debug Boo compiled assemblies and step through them just fine in the dbgclr.exe.

Is dbgclr.exe just more error tolerant, or might it be a difference in the way .pdb files are handled in .NET 1.1 vs 2.0?

Show
Arron Washington added a comment - I can debug Boo compiled assemblies and step through them just fine in the dbgclr.exe. Is dbgclr.exe just more error tolerant, or might it be a difference in the way .pdb files are handled in .NET 1.1 vs 2.0?
Hide
Permalink
Daniel Grunwald added a comment -

DbgCLR from .NET 2.0 Beta 2 prints "No symbols are available for this location" when stepping onto anything different than a "for" loop.
Breakpoints placed onto anything else than a "for" loop disappear when starting the program.

Show
Daniel Grunwald added a comment - DbgCLR from .NET 2.0 Beta 2 prints "No symbols are available for this location" when stepping onto anything different than a "for" loop. Breakpoints placed onto anything else than a "for" loop disappear when starting the program.
Hide
Permalink
Rodrigo B. de Oliveira added a comment -

AFAICS it works as long as you use the latest binaries.

Show
Rodrigo B. de Oliveira added a comment - AFAICS it works as long as you use the latest binaries.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.