Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA 0/3] Fix various bugs found by static analysis
Date: Tue, 04 Oct 2016 15:14:00 -0000	[thread overview]
Message-ID: <CAH=s-PM=1iJrBB_qAa_NY+yCNRJ1wDs135Aju_6J=aZW6A_Axg@mail.gmail.com> (raw)
In-Reply-To: <1475531646-18049-1-git-send-email-tom@tromey.com>

On Mon, Oct 3, 2016 at 10:54 PM, Tom Tromey <tom@tromey.com> wrote:
>
> * PR 20654, incorrect code in java_value_print.  Now that gcj has been
>   removed, I think it's probably better to simply remove the Java
>   language support.  If this sounds ok, let me know, and I can provide
>   a patch.
>

I am fine to remove java language support in GDB, but I'd like to hear
what other people think about this.

-- 
Yao (齐尧)


  parent reply	other threads:[~2016-10-04 15:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 21:54 Tom Tromey
2016-10-03 21:54 ` [RFA 3/3] PR remote/20655 - small fix in handle_tracepoint_bkpts Tom Tromey
2016-10-04 12:53   ` Yao Qi
2016-10-03 21:54 ` [RFA 1/3] PR symtab/20652 - fix psymbol_compare Tom Tromey
2016-10-04 10:55   ` Yao Qi
2016-10-04 18:37   ` Pedro Alves
2016-10-04 18:52     ` Tom Tromey
2016-10-03 21:54 ` [RFA 2/3] PR gdb/20653 - small cleanup in string_to_explicit_location Tom Tromey
2016-10-03 22:27   ` Keith Seitz
2016-10-04 10:50   ` Yao Qi
2016-10-04 15:14 ` Yao Qi [this message]
2016-10-04 18:31   ` [RFA 0/3] Fix various bugs found by static analysis Pedro Alves
2016-10-04 19:05     ` Eli Zaretskii
2016-10-04 20:43       ` Tom Tromey

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='CAH=s-PM=1iJrBB_qAa_NY+yCNRJ1wDs135Aju_6J=aZW6A_Axg@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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