** Description changed:

- OpenJDK 8 apport hook attaches the hs_err_pid<pid>.log (if it exists) to
- a Crash report under the HotspotError key. The hook is currently limited
- to attaching files under 100 KB.
+ [Impact] 
+ By default OpenJDK 8 generates an hs_err file when it crashes, this file 
contains the stacktrace generated by OpenJDK (thus it contains different data 
compared to a gdb stacktrace) plus information on the running threads, classes, 
and memory usage (OpenJDK's regions). This file is usually required by the 
OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case 
of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate 
from OpenJDK crashes.
+ 
+ OpenJDK 8 now includes a new apport hook to collect additional data from
+ crash reports as well as the hs_err log file (in the new HotspotError
+ key).
+ 
+ A new release is soon reaching Zesty and Xenial with the hook included
+ and without SRU'ing this fix the hs_err file won't be uploaded to the
+ error tracker.
+ 
+ [Test Case]
+ 1. Start any java program using OpenJDK 8
+ 2. Kill it with SIGILL
+ 3. Check that the created report contains the hs_err file
+ 
+ [Regression Potential] 
+ If the new key is added to acceptable_fields whoopsie will upload the entries 
in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to 
it could allow bigger files with in turn cause an overhead in the error tracker 
infrastructure.
+ 
+ [Original bug report]
+ OpenJDK 8 apport hook attaches the hs_err_pid<pid>.log (if it exists) to a 
Crash report under the HotspotError key. The hook is currently limited to 
attaching files under 100 KB.
  
  Please add HotspotError key to the whitelist in order for it to be
  available in error tracker.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1696814

Title:
  add openjdk hs log to list of acceptable_fields in whoopsie

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Xenial:
  Triaged
Status in whoopsie source package in Zesty:
  Triaged

Bug description:
  [Impact] 
  By default OpenJDK 8 generates an hs_err file when it crashes, this file 
contains the stacktrace generated by OpenJDK (thus it contains different data 
compared to a gdb stacktrace) plus information on the running threads, classes, 
and memory usage (OpenJDK's regions). This file is usually required by the 
OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case 
of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate 
from OpenJDK crashes.

  OpenJDK 8 now includes a new apport hook to collect additional data
  from crash reports as well as the hs_err log file (in the new
  HotspotError key).

  A new release is soon reaching Zesty and Xenial with the hook included
  and without SRU'ing this fix the hs_err file won't be uploaded to the
  error tracker.

  [Test Case]
  1. Start any java program using OpenJDK 8
  2. Kill it with SIGILL
  3. Check that the created report contains the hs_err file

  [Regression Potential] 
  If the new key is added to acceptable_fields whoopsie will upload the entries 
in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to 
it could allow bigger files with in turn cause an overhead in the error tracker 
infrastructure.

  [Original bug report]
  OpenJDK 8 apport hook attaches the hs_err_pid<pid>.log (if it exists) to a 
Crash report under the HotspotError key. The hook is currently limited to 
attaching files under 100 KB.

  Please add HotspotError key to the whitelist in order for it to be
  available in error tracker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to