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?
--
gdb crashed with SIGSEGV in iterate_over_threads()
https://bugs.launchpad.net/bugs/258578
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
