Skip to content

cueprint: Manpage promises null-byte-escape support, it seems it is recognized but incorrectly handled while output #26

@ghost

Description

Fowarded from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548224
(The bug is still present in v1.4.1)

Manpage promises null-byte-escape support (\0 esc-sequence) in the
"template-strings",

Escapes
The recognized escapes are all single characters, and listed in the
table below.

   Escape Sequence   Expansion
   ----------------------------------
   \a                alert (bell)
   \b                backspace
   \f                formfeed
   \n                newline
   \r                carriage return
   \t                horizontal tab
   \v                vertical tab
   \0                null

it seems like sequence is recognized but incorrectly
handled while output (looks like code tries to do printf() with char[]
containing null-chars).

Sample runs:

$ cueprint -d '%P\n%T\n' disc_1.cue
Emerson String Quartet
Schubert - Streichquartette - Emerson
$

$ cueprint -d '%P\0%T\n' disc_1.cue
Emerson String Quartet$

$ cueprint -d '%P\n\0%T\n' disc_1.cue
Emerson String Quartet
$

(The original submitter didn't provided disc_1.cue, but it should be easy to create a testcase.)
$ cat disc_1.cue
PERFORMER "Emerson String Quartet"
TITLE "Schubert - Streichquartette - Emerson"
FILE "01.wav" WAVE
TRACK 01 AUDIO
TITLE "001"
PERFORMER "test"
PREGAP 00:00:32
INDEX 01 00:00:00

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions