Skip to content

Libmbc: Issue in limited size of the socket path variable

Hi everyone,

using the socket functionality of the MBDyn Python interface, I found an issue regarding the size of the passed path variable, which is passing the socket path to the interface.

The variable is passed via the interface of the library libmbc here as path in the init function. Moving on, it is getting processed here in int mbdyn_make_named_socket_type() as path.

The issue I am facing is that the path var, or something within the further processing, is limiting the size of the path to 107 characters. When passing >107 characters, the script just waits forever withot any error message after printing: "connecting to path=/somepathwith108characters.sock timeout=forever".

Maybe this is something which can be fixed in the future. Using absolute paths, it would be nice to have more than 107 characters to describe the path to the socket. Also throwing an error after receiving too much characters would simplify debugging.

Yours

Julian

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information