Ticket #987 (assigned bug)

Opened 7 years ago

Last modified 6 years ago

Make breakpoints actually work in parrot_debugger

Reported by: dukeleto Owned by: Paul C. Anagnostopoulos
Priority: normal Milestone:
Component: tools Version: 1.5.0
Severity: medium Keywords: tools debugger
Cc: Language:
Patch status: Platform: all


Currently, you can add and delete breakpoints, but they don't actually stop the program flow.

A failing test for this would be a good start.

Change History

Changed 7 years ago by jkeenan

  • owner set to dukeleto
  • component changed from none to tools

Changed 6 years ago by Paul C. Anagnostopoulos

  • status changed from new to assigned
  • owner changed from dukeleto to Paul C. Anagnostopoulos

Changed 6 years ago by Paul C. Anagnostopoulos

Actually, breakpoints do work now, although not perfectly. There are some other problems that could stand fixing, so I'm working on them now.

Changed 6 years ago by Paul C. Anagnostopoulos

The first round of improvements was committed in r49021. This includes fixes to source file loading, source/disassembly listing, and breakpoints. Note that the code PCs in the source listing are incorrect; use the disassembly listing to set breakpoints.

Changed 6 years ago by jkeenan

  • keywords debugger added

Any GSOC candidates interested in working on Parrot debugger should review this ticket.

Note: See TracTickets for help on using tickets.