No javascript debugging and some files get deleted

[GoogleCodeExporter]

Google Chrome version: 3.0.196.2
SDK + Eclipse Debugger version(s): 0.1.0.200907271854
OS + version: WinXP SP3

What steps will reproduce the problem?
1. Run a webapp localy with maven jetty:run
2. User chrome to view the localy hosted project 
(http://localhost:8080/projectname)

What is the expected result?
Have javascript debuging informations

What happens instead?
I only get the protocol messages at the console and after a while all files 
from the project get's deleted

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

Original issue reported on code.google.com by valo...@gmail.com on 5 Aug 2009 at 8:01

[GoogleCodeExporter]

valotas,

Is this issue consistently repeatable for you?

The target Debug JavaScript project contents do get deleted every time you 
connect to 
a Chromium instance anew, before loading the JS source of the tab you are 
attaching 
to, so this behaviour is expected.

Have you tried waiting a bit more for the JS sources to get loaded? Had the 
progress 
indicator stopped by the moment you saw no files in the project contents?

Can you please attach the console contents (with the protocol messages) at the 
moment 
the debug connection was fully established?

Original comment by apav...@chromium.org on 12 Aug 2009 at 9:15

[GoogleCodeExporter]

Yes I've tested with various projects. One think I dont understand is what 
should be 
the target debug javascript project. Should be a project containing the 
javascript 
files to be debugged or any project that will be used by eclipse just for the 
debugging?

If the first is true how can someone debug an existing project if it is ok to 
get 
deleted?

Original comment by valo...@gmail.com on 17 Aug 2009 at 9:59

[GoogleCodeExporter]

The target project is described in the how-to steps as "a project where the 
browser 
scripts will be stored". This means that this project will be created 
automatically by 
the debugger and filled in by the scripts that the debugger retrieves from the 
browser 
tab being debugged. You need not create this project by hand as its contents 
will be 
scratched once the connection is established.

Currently the debugger is not capable of using an existing project JS sources 
even 
though we are considering something similar to be implemented some time.

Original comment by pavlo...@gmail.com on 18 Aug 2009 at 9:30

[GoogleCodeExporter]

The described behavior is expected.

Original comment by apav...@chromium.org on 11 Sep 2009 at 1:06

• Changed state: Invalid