[c++] Function overloading causes call graph to use the wrong function

[freemedom]

Describe the bug
Function overloading causes call graph to use the wrong function

Screenshots

To Reproduce
testDoxygen.zip

static bool setup_bcb(const int socket) {
......
    std::vector<std::string> options = android::base::Split(content, "\n");
    std::string wipe_package;
    for (auto& option : options) {
        if (android::base::StartsWith(option, "--wipe_package=")) {
            std::string path = option.substr(strlen("--wipe_package="));
            if (!android::base::ReadFileToString(path, &wipe_package)) {
                PLOG(ERROR) << "failed to read " << path;
                return false;
            }
            option = android::base::StringPrintf("--wipe_package_size=%zu", wipe_package.size());
        }
    }

    // c8. setup the bcb command
    std::string err;
    if (!write_bootloader_message(options, &err)) { // <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
        LOG(ERROR) << "failed to set bootloader message: " << err;
        write_status_to_socket(-1, socket);
        return false;
    }
......
}

Expected behavior
use bool write_bootloader_message(const std::vector<std::string>& options, std::string* err) not bool write_bootloader_message(const bootloader_message& boot, std::string* err)

Version
1.10.0 (ebc57c6)

Stack trace

Additional context

[albert-github]

When I understand it correctly you mean that in the call graph of setup_bcb the reference to write_bootloader_message should not point to the 1/3 overload of write_bootloader_message but to the 3/3 overload.

This is indeed not correct but also a known issue.

The settings file is missing,, I could reproduce the problem with the settings:

QUIET = YES
EXTRACT_ALL = YES
EXTRACT_STATIC = YES
RECURSIVE = YES
HAVE_DOT = YES
CALL_GRAPH = YES
CALLER_GRAPH = YES

in future please always add the settings (the result of doxygen -x Doxyfile to the example.

[freemedom]

@albert-github Yes, that's what I mean. (I'm not very good at English.)