Bug#436892: gdb-doc: Java support is completely undocumented (was: Re: Bug#436892: gdb: Java is completely broken)

2014-06-13 Thread Samuel Bronson
Control: retitle -1 Java support is completely undocumented Control: reassign -1 gdb-doc Control: found -1 gdb-doc/6.4.90-1 gdb-doc/7.1-1 Control: affects -1 gdb Daniel Jacobowitz writes: > On Fri, Aug 10, 2007 at 07:23:14PM +1000, Lashi wrote: >> But where do I set the breakpoint? I mean this s

Bug#436892: gdb: Java is completely broken

2007-08-10 Thread Daniel Jacobowitz
On Fri, Aug 10, 2007 at 07:23:14PM +1000, Lashi wrote: > On Thu, 2007-08-09 at 07:33 -0400, Daniel Jacobowitz wrote: > > This isn't completely broken, it's just ugly. You're in the generated > > main which will call the argument to --main. Set a breakpoint there > > and continue, and you'll reach

Bug#436892: gdb: Java is completely broken

2007-08-09 Thread Daniel Jacobowitz
On Thu, Aug 09, 2007 at 08:02:03PM +1000, Menaka Lashitha Bandara wrote: > (gdb) list > 1 /tmp/ccRas48v.i: No such file or directory. > in /tmp/ccRas48v.i > (gdb) This isn't completely broken, it's just ugly. You're in the generated main which will call the argument to --main. Set

Bug#436892: gdb: Java is completely broken

2007-08-09 Thread Menaka Lashitha Bandara
Package: gdb Version: 6.4.90.dfsg-1 Severity: important I've uncovered quite a big problem in gdb when attempting to debug Java. Firstly, here's the source code of Test.java: class Test { public static void main (String[] args) { System.out.println ("He