RFR (S): 8193258: Better usage of JDWP HEADER SIZE

Langer, Christoph christoph.langer at sap.com
Fri Dec 8 21:07:06 UTC 2017


Hi Serguei,

I did only run hotspot/jtreg/serviceability/jdwp, didn’t find a lot more in that area. I’m hoping/waiting for Chris’ tests then.

I agree, I will then remove inStream_endOfInput. If something like that is needed for future developments, it can easily be added again.


Best regards
Christoph

From: serguei.spitsyn at oracle.com [mailto:serguei.spitsyn at oracle.com]
Sent: Freitag, 8. Dezember 2017 21:12
To: Langer, Christoph <christoph.langer at sap.com>; serviceability-dev at openjdk.java.net; Chris Plummer <chris.plummer at oracle.com>
Subject: Re: RFR (S): 8193258: Better usage of JDWP HEADER SIZE

Hi Christoph,

The fix looks good to me.
What tests did you run?


On 12/8/17 07:07, Langer, Christoph wrote:
Hi,

Here’s a proposal to clean up the usage of the JDWP header size within the source code of libjdwp.

Bug: https://bugs.openjdk.java.net/browse/JDK-8193258
WebRev: http://cr.openjdk.java.net/~clanger/webrevs/8193258.0/<http://cr.openjdk.java.net/%7Eclanger/webrevs/8193258.0/>

As for inStream.c, I’m wondering wether inStream_endOfInput shall be removed? It seems to be unused…

I'm inclined to remove it.
Otherwise, it must be:
  417 return (stream->left <= 0);

Thanks,
Serguei

Best regards
Christoph


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20171208/6285db61/attachment-0001.html>


More information about the serviceability-dev mailing list