Some questions

Thu Jul 12 05:32:00 GMT 2001

Mark Wielaard writes:
 > Hi,
 > 
 > On Thu, Jul 12, 2001 at 01:04:11PM +0100, Andrew Haley wrote:
 > > Mark Wielaard writes:
 > > > This looks a bit like the bug discussed in
 > > > < http://gcc.gnu.org/ml/java/2001-05/msg00277.html >
 > > > < http://gcc.gnu.org/ml/java/2001-06/msg00003.html >
 > > > 
 > > > Maybe the patch in those emails helps?
 > > 
 > > > Note that I don't know exactly why it fixes the problem in that case
 > > > and nobody else seems to have looked at it.
 > > 
 > > I don't think that the patch can be correct. We need to find out why
 > > _Jv_FindClass returns null in this case. I've never seen this happen.
 > The second email give a way to reproduce it. But the test case described
 > there is much to big to be practical.
Oh yes, you're perfectly correct here. Sorry.
 > > > > How do you guys debug? Where do i have to set a breakpoint and in which
 > > > > thread?
 > > 
 > > I don't understand the issue here. Surely all that is required is to
 > > add a line like 
 > > 
 > > if (catch_type = NULL)
 > > printf ("BANG\n");
 > > 
 > > and use gdb to put a breakpoint on that line. Are you not familiar
 > > with gdb?
 > The issue here is indeed my unfamiliarity with gdb combined with
 > the huge test senario described above. If someone could describe a
 > walkthrough on how to (begin) debugging something like this that
 > would be greatly appreciated.
Well, debugging exception handling code is hard, even for someone very
experienced.
 > To be honest I always find working on/with (lib)gcj a bit
 > intimidating since the build process alone takes up 45 minutes on
 > my machine (yes I should buy something faster if I have the money
 > :) And coming from a java background (and some Haskell and other
 > modern functional/logic languages) the combination of
 > C/C++/automake/libtool etc is really confusing.
 > 
 > I am willing to learn, but this will take some time :)
Okay. I'd suggest at least working through the sample gdb session
described in 'info gdb'. Then, once you have some familiarity with
gdb, we'll talk some more.
Andrew.