From 8280885d56a301562c4e9b16e52c05afb3344ed3 Mon Sep 17 00:00:00 2001 From: perrywangpartner Date: Mon, 16 Mar 2026 10:24:30 +0800 Subject: [PATCH] Enhance log when adding diagnostic jobs When add or remove UDS diagnostic jobs to DiagJobRoot, It is necessary to record whether the action was successful. --- libs/bsw/uds/src/uds/base/AbstractDiagJob.cpp | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/libs/bsw/uds/src/uds/base/AbstractDiagJob.cpp b/libs/bsw/uds/src/uds/base/AbstractDiagJob.cpp index ab4b7172c98..17dd4034446 100644 --- a/libs/bsw/uds/src/uds/base/AbstractDiagJob.cpp +++ b/libs/bsw/uds/src/uds/base/AbstractDiagJob.cpp @@ -187,6 +187,9 @@ AbstractDiagJob::ErrorCode AbstractDiagJob::addAbstractDiagJob(AbstractDiagJob& } job.fpNextJob = nullptr; job.fpFirstChild = nullptr; + + Logger::debug(UDS, "Add diag job successfully 0x%X", job.getRequestId()); + return JOB_ADDED; } if (job.isFamily(fpImplementedRequest, static_cast(fRequestLength))) @@ -215,6 +218,8 @@ void AbstractDiagJob::removeAbstractDiagJob(AbstractDiagJob& job) if (&job == fpFirstChild) { // we remove our first child fpFirstChild = job.getNextJob(); + + Logger::debug(UDS, "Remove diag job successfully 0x%X", job.getRequestId()); return; }