The -L flag should not exist

Why does the -L flag exist? The .hp file should contain untruncated strings, and any truncation of the names should be done in hp2ps.

Trac metadata

Trac field	Value
Version	7.2.1
Type	Bug
TypeOfFailure	OtherFailure
Priority	normal
Resolution	Unresolved
Component	Profiling
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture

mentioned in issue #3024 (closed)

changed weight to 5

added Tbug Trac import profiling labels

changed milestone to %7.6.1

changed milestone to %7.6.2

Does having a milestone imply that this is a desired feature and just waits for implementation? Might be some low hanging fruit for a bypassing contributor.

It means we think the suggestion is sensible, but with a priority of "normal" it isn't likely to get done by us (we only tend to get to the "high" stuff).

Regarding this ticket specifically, hp2ps needs to be thrown away and rewritten in Haskell. Last I heard hp2pretty wasn't quite there yet.

Trac metadata

Trac field	Value
BlockedBy	→ #3024 (closed)

changed milestone to %7.10.1

Moving to 7.10.1.

For reference, in commit 16871485:

Author: Ravi Nanavati <>
Date:   Fri Sep 29 22:51:15 2006 +0000

    rts_ccs_length
    
    Add the -L RTS flag to control the length of the cost-centre stacks reported in
    a heap profile.

And in rts/RtsFlags.c:

 "  -L<chars>      Maximum length of a cost-centre stack in a heap profile",
 "                 (default: 25)",

Undocumented as far as I can tell in the user's guide.

removed milestone

Moving to 7.12.1 milestone; if you feel this is an error and should be addressed sooner, please move it back to the 7.10.1 milestone.

changed milestone to %8.0.1

Milestone renamed

mentioned in commit 923d2151

I agree that we shouldn't truncate the cost centre names. Removing the flag sounds like the best option here and move all responsibility to tools. I should check whether the -L flag also truncates the names of cost centres in the eventlog as well.

added newcomer label

@mpickering I'm pretty certain I circumvented the truncation logic for the eventlog output; avoiding truncation was one of the my initial motivations for implementing eventlog output.