public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/6092: sparc-sun-solaris2.7 has hundreds of libjava failures with -m64 Date: Wed, 10 Apr 2002 18:06:00 -0000 [thread overview] Message-ID: <20020411010602.5448.qmail@sources.redhat.com> (raw) The following reply was made to PR java/6092; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> Cc: gcc-gnats@gcc.gnu.org, hans_boehm@hp.com Subject: Re: java/6092: sparc-sun-solaris2.7 has hundreds of libjava failures with -m64 Date: 10 Apr 2002 18:59:33 -0600 >>>>> "Kaveh" == Kaveh R Ghazi <ghazi@caip.rutgers.edu> writes: Kaveh> One is that it must be running solaris2.7 or later for gcc to Kaveh> configure 64 bit. Today I managed to build this toolchain and see the failure. It wasn't as easy as I was expecting, partly due to local conditions and partly because dejagnu didn't automatically run the -m64 tests; I had to figure out how to ask it to do that. I found a gdb here that seems to know how to debug on this machine. It gives me the appended stack trace. Hans, any clues you can give me on debugging this would be helpful. Tom (gdb) bt #0 0xfffffeab7ed6fd50 in ?? () #1 0xffffffff7ed68f20 in GC_stopped_mark ( stop_func=0xffffffff7ed68598 <GC_never_stop_func>) at ../../../../gcc/boehm-gc/alloc.c:489 #2 0xffffffff7ed68b88 in GC_try_to_collect_inner ( stop_func=0xffffffff7ed68598 <GC_never_stop_func>) at ../../../../gcc/boehm-gc/alloc.c:350 #3 0xffffffff7ed72de0 in GC_init_inner () at ../../../../gcc/boehm-gc/misc.c:673 #4 0xffffffff7ed72a60 in GC_init () at ../../../../gcc/boehm-gc/misc.c:455 #5 0xffffffff7ed6cce4 in GC_init_gcj_malloc (mp_index=32752, mp=0xffffffff7ed655e4) at ../../../../gcc/boehm-gc/gcj_mlc.c:62 #6 0xffffffff7ed6636c in _Jv_InitGC() () at ../../../../gcc/libjava/boehm.cc:465 #7 0xffffffff7ebe6520 in _Jv_CreateJavaVM(void*) () at ../../../../gcc/libjava/prims.cc:892 #8 0xffffffff7ebe69b0 in _Jv_RunMain(java::lang::Class*, char const*, int, char const**, bool) (klass=0x100102518, name=0x0, argc=1, argv=0xffffffff7ffff718, is_jar=false) at ../../../../gcc/libjava/prims.cc:982 #9 0x100001820 in main ()
next reply other threads:[~2002-04-11 1:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-10 18:06 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-30 22:06 Kaveh R. Ghazi 2002-03-30 21:46 Tom Tromey 2002-03-30 21:26 Kaveh R. Ghazi 2002-03-30 14:56 Tom Tromey 2002-03-30 12:36 Kaveh R. Ghazi 2002-03-29 11:16 Tom Tromey 2002-03-29 11:06 Kaveh R. Ghazi 2002-03-29 8:56 Tom Tromey 2002-03-29 8:16 ghazi
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020411010602.5448.qmail@sources.redhat.com \ --to=tromey@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).