Closed freeze-dolphin closed 9 months ago
I think the length of the string may not be to blame for the problem.
As we could see the debug log has contained the whole string.
libcyaml: DEBUG: Load: Event: SCALAR
libcyaml: DEBUG: Load: Handle state in mapping (value)
libcyaml: DEBUG: Load: Reading value of type 'STRING' (pointer)
libcyaml: DEBUG: Load: Allocation: 0x55846e71a330 (0 + 35 bytes)
libcyaml: INFO: Load: <∞I CAN'T FUCKING MAKE STREAMS∞>
But why? Why does it work when the string was cut?
I found out that this is not the duty of libcyaml, it's another lib: zip
Here is my schema:
And when I was processing this yaml:
I found that the program kept crashing with
malloc(): invalid next size (unsorted)
.I tried shorten the string field
alias
(it looks very suspicious...).After cutting it in half like this:
Then the program ran normally.
And I'm just wondering why... I have set the
CYAML_UNLIMITED
for this field.Here is the output with the log level debug: