Skip to content

docs: fix four broken links #853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
castler merged 1 commit into from
Aug 5, 2026
Merged

docs: fix four broken links #853

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions score/memory/shared/design/OffsetPtrDesign.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`.
Expand Down
2 changes: 1 addition & 1 deletion score/memory/shared/design/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion score/mw/com/dependability/software_architectural_design/method/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading