ENSIME debugger guidance

[Curt Brune]

Hi -

First off -- ensime is pretty cool. I really like what I've seen so
far. Thanks for your work.

I am a total newbie to ensime and need some guidance with the
debugger. I'm using ensime version ensime_2.9.2-RC1-0.9.3.RC4.

I read the manual, but still have some questions. Forgive me if this
old stuff.

question1 - Is there a real difference between ensime-db-start and
ensime-db-run ? They seem to do the same thing for me -- they both
start the program in the debugger and run until a break point is hit.

question2 - While in the debugger where does the stdout from print()
go? From an sbt shell I can see the output, but in the debugger I
don't see the printing.

question3 - The manual talks about a buffer named *ensime-db*, but I
don't see one. Should there be some kind of debugger output buffer?

Cheers,
Curt

[Aemon Cannon]

Hiya,

run will invoke start if there's no active vm. after that run is synonymous with continue.. and start makes no sense,

so they _are_ different, but only in a confusing way : )

I haven't figured out how to get the stdout yet! i think it's a simple thing i'm doing wrong.. (see DebugManager.scala)

*ensime-db* is deprecated. I'm working on a top-level debug status view.. but for now, you just have the backtrace, object inspector.

Best,

Aemon

[Curt Brune]

I think the output stream needed to be flushed.  I added this:

out.flush

after the out.write() in MonitorOutput() and the output now shows in the *inferior-ensime-server* buffer.

Cheers,

Curt

[Aemon Cannon]

Ah, there it is.

In latest scala-2.9 branch, i'm sending output to client, and writing to *ensime-db-output-buffer*.

May add support for redirecting to file at some point.

Cheers,

Aemon