Packing with musl causes segfault

[1c3t3a]

Packing with musl causes segfault

[1c3t3a]

Did you experience with an earlier version as well?

[editso]

Did you experience with an earlier version as well?

Yes, I used 0.2.4 earlier but this version has the same error

[1c3t3a]

Oke, first of all are you sure the server is configured correctly? The url mentions a /ws/, does it help to connect via ws:// instead of http://, are you sure the node namespace exists? Could you also explain more about your environment, I am not really familiar with it. I expect that in your environment there are no formatting outputs, are there? This would help to further narrow down the problem (e.g. something like special unwrap errors on a result).

[editso]

Oke, first of all are you sure the server is configured correctly? The url mentions a /ws/, does it help to connect via ws:// instead of http://, are you sure the node namespace exists? Could you also explain more about your environment, I am not really familiar with it. I expect that in your environment there are no formatting outputs, are there? This would help to further narrow down the problem (e.g. something like special unwrap errors on a result).

As long as I don't use musl for packing I don't have any problems

[editso]

Oke, first of all are you sure the server is configured correctly? The url mentions a /ws/, does it help to connect via ws:// instead of http://, are you sure the node namespace exists? Could you also explain more about your environment, I am not really familiar with it. I expect that in your environment there are no formatting outputs, are there? This would help to further narrow down the problem (e.g. something like special unwrap errors on a result).

As long as I don't use musl for packing I don't have any problems

I don't think it should have a segment error even if it is caused by these problems

[editso]

Oke, first of all are you sure the server is configured correctly? The url mentions a /ws/, does it help to connect via ws:// instead of http://, are you sure the node namespace exists? Could you also explain more about your environment, I am not really familiar with it. I expect that in your environment there are no formatting outputs, are there? This would help to further narrow down the problem (e.g. something like special unwrap errors on a result).

The problem occurred when using musl packaging and I thought it was worth trying musl packaging to verify the problem

[editso]

Oke, first of all are you sure the server is configured correctly? The url mentions a /ws/, does it help to connect via ws:// instead of http://, are you sure the node namespace exists? Could you also explain more about your environment, I am not really familiar with it. I expect that in your environment there are no formatting outputs, are there? This would help to further narrow down the problem (e.g. something like special unwrap errors on a result).

The problem occurred when using musl packaging and I thought it was worth trying musl packaging to verify the problem

If necessary I will download your source code and try to debug it and find out what the problem is

[1c3t3a]

Do you have any updates on this? I don't really know the process of "packaging with musl", if you could further explain this I might be able to help