HTTP/1.1 -1 Read error in cache disk data: SuccessContent-Type: text/csv; charset="utf-8" Last-Modified: Sat, 22 Jan 2022 03:34:48 GMT Content-length: 1180 Connection: Close Proxy-Connection: Close X-Cache: HIT from web1.osuosl.org Server: ProxyTrack 0.5 (HTTrack 3.49.2) id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,lang,patch,platform 1430,Change trace offset numbers to hex format,Austin_Hastings,,"pbc_dump, as well as every other dumping tool on the planet, outputs in hex: {{{ 00c6: 00000025 00000034 get_params_pc 00cb: 000003d1 00000000 00000002 00000039 set_p_p_kc 00cf: 0000014c 00000000 00000006 unless_null_p_ic }}} but trace outputs offset numbers in decimal: {{{ 198 get_params PC52 (3), P1, P3, P2 PC52=FixedIntegerArray=PMC(0x81f09d8) P1=PMCNULL P3=PMCNULL P2=PMCNULL 203 set P0, P2[""to""] P0=PMCNULL P2=Hash=PMC(0x818ee10) 207 unless_null P0, 6 P0=PMCProxy=PMC(0x818f950) }}} Not that I _can't_ do decimal-to-hex conversions in my head in real time, or anything. But _other people_ might find the tools easier to use if they were consistent. ",cage,closed,normal,,none,2.0.0,medium,done,"parrot, trace, format, hexadecimal",,,, common/js/jquery