Comment 11 for bug 258578

Revision history for this message
halfdog (halfdog) wrote :

Also happens with sun java 6: gdb --args /usr/bin/java on hardy lts with sun java6 SE

Could it be related to

      if (stop_soon == STOP_QUIETLY || stop_soon == NO_STOP_QUIETLY)
        {
          resume (0, TARGET_SIGNAL_0);

which sounds like true || false, while further down the code the pattern

      stop_soon == STOP_QUIETLY || stop_soon == STOP_QUIETLY_NO_SIGSTOP

is used?

Apart from that: It seems that suse linux gdb is not affected by that, Could it be that it is already fixed in an upstream version? Is source of suse packages available?