Linux环境下C++中TidyHtml无法正常工作的问题求助

Let's work through your two libtidy problems step by step:

1. tidyOptSetBool() Call Failing (printf("1") Never Executes) #

First, remember that tidyOptSetBool() returns a TidyStatus enum value—so the first step is to capture and inspect that return value to pinpoint why it's failing. Here's how to adjust your code to get actionable info:

#include <tidy/tidy.h>
#include <tidy/tidybuffio.h>

// ... your existing code ...

TidyDoc tidyDoc = tidyCreate();
if (!tidyDoc) {
    // Handle creation failure
    return 1;
}

// Capture the status of the option set call
TidyStatus optStatus = tidyOptSetBool(tidyDoc, "YOUR_OPTION_NAME", yes);
if (optStatus == SUCCESS) {
    printf("%s\n", "1");
} else {
    printf("tidyOptSetBool failed with status code: %d\n", optStatus);
    // Common status codes to check:
    // - NO_SUCH_OPTION: The option name you used is invalid/typo'd
    // - BAD_PARAM: The third argument isn't a valid boolean (use `yes` or `no` from tidy.h)
    // - NOT_AVAILABLE: The option isn't supported in your libtidy version
}

Next, verify these key points:

• Option Name Correctness: libtidy options are case-sensitive. For example, use TidyXhtmlOut instead of tidyxhtmlout. You can list all valid options for your libtidy version by calling tidyGetOptionList(tidyDoc) and iterating through the results, or check the tidy.h header file directly.
• Call Timing: You must call tidyOptSetBool() after tidyCreate() but before tidyParse() or tidyParseFile(). Configuration changes don't apply to already-parsed documents.
• Libtidy Version Compatibility: Some options get renamed or deprecated across versions. If you're using a newer libtidy release, double-check that your target option still exists.

2. tidyBufFree(&output) Exception #

Buffer-related errors usually stem from improper initialization or misuse of the tidyBuf structure. Here's how to fix common issues:

First, Ensure Proper Buffer Initialization #

Always initialize your tidyBuf before using it with libtidy functions:

tidyBuf output;
tidyBufInit(&output); // Critical step—don't skip this!

Validate Buffer Population #

Make sure tidySaveBuffer() (or whichever function fills the buffer) succeeds before trying to free it. If the save fails, the buffer may not have been allocated, leading to a free error:

TidyStatus saveStatus = tidySaveBuffer(tidyDoc, &output);
if (saveStatus != SUCCESS) {
    printf("Failed to save document to buffer: %d\n", saveStatus);
    tidyRelease(tidyDoc);
    tidyBufFree(&output); // Even if empty, init'd buffers should be freed
    return 1;
}

// Use the buffer content here...

// Now safely free it
tidyBufFree(&output);

Avoid Double-Freeing #

Never call tidyBufFree() on the same buffer more than once. If you're reusing the buffer, reset it with tidyBufClear(&output) instead of reinitializing or freeing again.

Clean Up Order Note #

The tidyBuf is independent of the TidyDoc—you can free the buffer anytime after you're done with its data, as long as it was properly initialized and populated. Just ensure you don't access the buffer content after calling tidyBufFree().

General Debugging Tips #

• Enable libtidy's internal logging to catch more context:

  tidyOptSetBool(tidyDoc, "TidyShowWarnings", yes);
  tidyOptSetInt(tidyDoc, "TidyWarningLevel", 4); // Max verbosity
  tidyOptSetBool(tidyDoc, "TidyShowErrors", yes);
  

• Always check the return values of all libtidy functions—they're designed to tell you when something goes wrong.

内容的提问来源于stack exchange，提问作者bandito40