From 95147ccd491cefcea1a6025023fe43c88d0c4ace Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?H=C3=BCseyin=20Kutsi=20Balc=C4=B1?= Date: Wed, 5 Aug 2026 19:38:38 +0300 Subject: [PATCH] docs: fix four broken links MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Three links under score/memory/shared/design/ use one ../ too many, so they resolve above the repository root and 404. The design docs sit at score/memory/shared/design/, which is three levels below score/, not four. One image link is written as hhttp:// instead of http://, so the PlantUML diagram for the method call does not render at all. The other diagram in the same file already uses http://www.plantuml.com. Signed-off-by: Hüseyin Kutsi Balcı --- score/memory/shared/design/OffsetPtrDesign.md | 4 ++-- score/memory/shared/design/README.md | 2 +- .../software_architectural_design/method/README.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/score/memory/shared/design/OffsetPtrDesign.md b/score/memory/shared/design/OffsetPtrDesign.md index c05859268e..92677a72c0 100644 --- a/score/memory/shared/design/OffsetPtrDesign.md +++ b/score/memory/shared/design/OffsetPtrDesign.md @@ -174,8 +174,8 @@ We rely on having sufficient tests to ensure that the implementation behaves as ### Bounds checking iterators / element access LoLa uses [DynamicArrays](../../../containers/dynamic_array.h) for -its [ServiceDataStorage](../../../../mw/com/impl/bindings/lola/service_data_storage.h) -and [ServiceDataControl](../../../../mw/com/impl/bindings/lola/service_data_control.h). +its [ServiceDataStorage](../../../mw/com/impl/bindings/lola/service_data_storage.h) +and [ServiceDataControl](../../../mw/com/impl/bindings/lola/service_data_control.h). A `DynamicArray` is a fixed-size array data structure whose size can be, dynamically set at construction. Since these both reside in shared memory, the underlying pointer type used by `DynamicArray` must be an `OffsetPtr`. The `DynamicArray` is therefore susceptible to similar issues of memory corruption as an `OffsetPtr`. diff --git a/score/memory/shared/design/README.md b/score/memory/shared/design/README.md index 52e0d917d6..043a8db828 100644 --- a/score/memory/shared/design/README.md +++ b/score/memory/shared/design/README.md @@ -5,7 +5,7 @@ an abstraction layer is introduced. ## Use Cases / Customer Functions There are no direct Customer Functions associated with this part of `ara::core`. This is caused by the fact that the shared memory abstraction represents an implementation detail, -which is necessary to fulfill the [Basic Architectural thoughts](../../../../mw/com/design/README.md) of `ara::com`. +which is necessary to fulfill the [Basic Architectural thoughts](../../../mw/com/design/README.md) of `ara::com`. In fact, the usage of shared memory or its allocators shall be fully transparent for a user of the `ara`-API. diff --git a/score/mw/com/dependability/software_architectural_design/method/README.md b/score/mw/com/dependability/software_architectural_design/method/README.md index efa6ed0a84..a863101d3d 100644 --- a/score/mw/com/dependability/software_architectural_design/method/README.md +++ b/score/mw/com/dependability/software_architectural_design/method/README.md @@ -156,7 +156,7 @@ Then the user provided service-method will be called with the `IN-args`/`OUT-arg When the user provided service-method-handler returns, it has already updated/set the `OUT-args` in the `METHOD`-shm-object. Then a reply-message is sent back via `message_passing` to the caller and the skeleton side is done with the processing of the method call and the thread will again wait for reception of a new call message. -![Process Call Method](hhttp://www.plantuml.com/plantuml/proxy?cache=no&src=https://raw.githubusercontent.com/eclipse-score/communication/master/score/mw/com/dependability/software_architectural_design/method/assets/process_method_call.puml) +![Process Call Method](http://www.plantuml.com/plantuml/proxy?cache=no&src=https://raw.githubusercontent.com/eclipse-score/communication/master/score/mw/com/dependability/software_architectural_design/method/assets/process_method_call.puml) #### Concluding call of method