Works here too :)
Cheers
Mario
On Sunday 08 January 2006 4:14 pm, Markus Barchfeld wrote:
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
se
On Sun, Jan 08, 2006 at 04:14:08PM +0100, Markus Barchfeld wrote:
> >What I've done
> >- I've replaced Matthias-patched eclipseDebug.rb
> >- I've hand performed the patching (just replaced the statements with the
> >new one by copy-n-paste)
> >- Run the usual test program and tried to ispect the
Mario Scalas wrote:
HI Markus, Matthias
My patch command says that the patch is malformed at line 10 :S
It seems as if two lines got joined accidently. I've created the patch
on eclipseDebug.rb with Team->create patch..., copy to clipboard and
then unchecked the two options und used uni
On Wed, Jan 04, 2006 at 01:44:14PM +0100, Mario Scalas wrote:
> Result:
> - No way :( I enabled debug logging on console and I got this:
> http://cdg.di.uniba.it/~mscalas/eclipse_ruby_inspect.png . Perhaps those ".."
> in objectId="0x..fdbec800c" matter?
I'got exactly the same problem in 1.8.3
HI Markus, Matthias
My patch command says that the patch is malformed at line 10 :S
What I've done
- I've replaced Matthias-patched eclipseDebug.rb
- I've hand performed the patching (just replaced the statements with the new
one by copy-n-paste)
- Run the usual test program and tried to
Matthias Berndt wrote:
On Sat, Dec 31, 2005 at 04:03:54PM +0100, Mario Scalas wrote:
What happens:
1) I put a breakpoint after I create an object of some class
2) In the debugger "variables" view I can see the variable with the '+' (well,
an arrow under GTK, meaning I can expand it)
3) I cl
On Sat, Dec 31, 2005 at 04:03:54PM +0100, Mario Scalas wrote:
> What happens:
> 1) I put a breakpoint after I create an object of some class
> 2) In the debugger "variables" view I can see the variable with the '+'
> (well,
> an arrow under GTK, meaning I can expand it)
> 3) I click upon the '+'
Hi Mario, Jim!
When I tried to reproduce the error with RDT 0.7.0RC1 and ruby 1.8.4 I
ran immediately into the segfault. After some hours of poking around in
the source code I found a patch to eval.c which avoids the segfault.
Unfortunately, I've no idea what ramifications the little hack has
Hi all,
I'm using the latest 0.7RC candidate of the RDT (under eclipse
3.1.1/linux/GTK/java5) and the problem in the mail's subject is really
annoying since I cannot effectively use the debugger for something more
complex than an "hello world" app :S
What happens:
1) I put a breakpoint
