Changelog for ghc-events-0.15.1
Change Log
0.15.1 - 2020-12-30
- Add missing extra-source-files #71
0.15.0 - 2020-12-16
- Add support for ticky-ticky counts #67
0.14.0 - 2020-11-17
- Add support for non-moving GC events #60
- Fix the parser error under GHC 9.0 #64
- Fix string encodings #62
- Switch to GitHub Actions #65, dropping GHC 7.8.4 from the support range
0.13.0 - 2020-04-04
- Fix broken UTF-8 decoding (#55)
- This is a breaking change. Most of the String fields in EventInfo have been replaced with Texts.
- Support GHC 8.10.1
0.12.0 - 2019-12-02
- Add support for EVENT_USER_BINARY_MSG (#54)
0.11.0 - 2019-10-29
- Add support for time profiling events (ProfSampleCostCetre and ProfBegin) (#53)
0.10.0 - 2019-10-01
- Add support for HeapProfSampleEnd and HeapBioProfSampleBegin (#52)
0.9.1 - 2019-09-03
0.9.0 - 2019-05-15
- Support the newly added par_balanced_copied field (#47)
0.8.0.2 - 2019-04-02
- Tighten lower version bound for base (#46)
0.8.0.1 - 2018-10-22
- Relax upper version bound for base to support GHC 8.6
- Relax upper version bound for binary
0.8.0 - 2018-07-11
0.7.3 - 2018-07-10
0.7.2 - 2018-03-13
- Add Semigroup instance for MaxVars to build with ghc-8.4
0.7.1 - 2018-02-17
- Export HeapProfBreakdown, HeapProfFlags, and PID types (#35)
0.7.0 - 2017-10-04
- Add support for heap profiling events (#29)
0.6.0 - 2017-05-31
This contains breaking changes.
- The deprecation notice on
readEventLogFromFile
has been retracted - The incremental API has been refactored
The details are as follows:
- Update bug tracker URL (#10)
- New test for Eden events (#11)
- Relax version bound for binary (#15)
- Enable Travis CI (#19)
- Refactor the incremental API which was introduced in 0.5.0.0 (#22)
- Some speed/memory usage improvements (#18, #22)
0.5.0.0 - unreleased
- Readme added :)
- Old parser replaced with an incremental implementation
- General overhaul of the codebase
- Partial Haddock coverage
The 0.5.* releases should be able to handle large event logs and logs that have been cut off abruptly, e.g. from executable runs that resulted in crashes.
This release should be mostly backwards compatible, however the "old" way of reading event logs, namely the readEventLogFromFile
function is now deprecated.
NOTE: Users parsing large logs may notice that this version of the library is noticably slower than the older versions. The incremental parser is at fault here - previous versions of the libray used a "trick" that would let them essentially skip the first step of the mergesort algorithm since EventBlock
s were already sorted in time order. The new parser reads the file incrementally and cannot take the advantage of this. Apologies for any inconvenience this may have caused.