From: Jie Liu <lj8175@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: java-patches@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Joel Sherrill <joel.sherrill@oarcorp.com>
Subject: Re: [PATCH] [JAVA] Double.parseDouble(null) throw NullPointerException
Date: Fri, 12 Aug 2011 17:12:00 -0000 [thread overview]
Message-ID: <CABc96T939QWVZw0fqAiDeCNLJY2n1xWzN3XFbdg2DgW2aQGvjA@mail.gmail.com> (raw)
In-Reply-To: <m3bovxqmc2.fsf@fleche.redhat.com>
> If you did, then I don't know, you'll have to debug it, sorry.
>
> I vaguely recollect that -fcheck-references adds a check for 'this' at
> the start of final methods. If I'm misremembering, then that is
> probably the problem.
In my debug, there appears no check for 'this' at start of String.length():
(gdb) s
java::lang::VMDouble::parseDouble (str=0x0)
at ../../../gcc-trunk/libjava/java/lang/natVMDouble.cc:165
165 int length = str->length();
(gdb) s
java.lang.String.length()int (this=@336e44)
at /mnt/gcj/gcj-rtems-work/gcc-trunk/libjava/java/lang/String.java:451
451 return count;
(gdb) p count
$5 = -268370093
(gdb) p this
$6 = (java.lang.String *) 0x0
Thanks,
Jie
next prev parent reply other threads:[~2011-08-12 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABc96T_0THd_tKzdHSjD-xcPd7=dqoFkr0aRwrdvx-h4s2Hnxg@mail.gmail.com>
2011-08-07 11:00 ` Jie Liu
2011-08-08 14:16 ` Tom Tromey
2011-08-09 17:29 ` Jie Liu
2011-08-10 13:34 ` Tom Tromey
2011-08-10 15:59 ` Jie Liu
2011-08-10 16:41 ` Tom Tromey
2011-08-12 7:39 ` Jie Liu
2011-08-12 16:22 ` Bryce McKinlay
2011-08-12 17:12 ` Jie Liu [this message]
2011-08-14 13:04 ` Tom Tromey
2011-08-15 14:07 ` Andrew Haley
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=CABc96T939QWVZw0fqAiDeCNLJY2n1xWzN3XFbdg2DgW2aQGvjA@mail.gmail.com \
--to=lj8175@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=joel.sherrill@oarcorp.com \
--cc=tromey@redhat.com \
/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: link
Be 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).