search

amostl / chromedevtools

Automatically exported from code.google.com/p/chromedevtools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Disconnecting the debugger removes all breakpoints #30

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Google Chrome version: 5.0.375.99
SDK + Eclipse Debugger version(s): 3.6/0.1.4.201001121950
OS + version: MacOSX Snow Leopard

What steps will reproduce the problem?
1. Connect the debugger to Chrome
2. Set some breakpoints in the scripts loaded into the New_configuration project
3. Disconnect (via Terminate or Disconnect)

What is the expected result?
The breakpoints remain set in the editor and in the Breakpoints view

What happens instead?
The breakpoints are gone, but oddly, the debugger in subsequent sessions stops 
on the corresponding lines

Please provide any additional information below. If possible, attach a
(reduced) test-case.

Original issue reported on code.google.com by ian.form...@gmail.com on 8 Jul 2010 at 4:28

GoogleCodeExporter commented 9 years ago 
This is expected to be fixed in next build.
It is already fixed in HEAD.

Original comment by peter.ry...@gmail.com on 8 Jul 2010 at 6:11

GoogleCodeExporter commented 9 years ago

Original comment by peter.ry...@gmail.com on 10 Aug 2010 at 8:37