Skip to content
This repository was archived by the owner on May 6, 2024. It is now read-only.
This repository was archived by the owner on May 6, 2024. It is now read-only.

Segmentation fault on arm64 #20

@islue

Description

@islue

Segmentation fault happens if I use 127.0.0.1 as node on arm64.
Instead, the local ip address works fine.
127.0.0.1 works fine on x86_64.

Here is my env, a t4g.micro ec2 instance with amzn2.

$ uname -a
Linux ip-10-1-100-13.ap-northeast-1.compute.internal 4.14.275-207.503.amzn2.aarch64 #1 SMP Wed Apr 13 20:24:49 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

$ cat /etc/proxy.conf 
port 8125
num_threads 2
flush_interval 100 # ms
socket_send_packet_size 8192

node 127.0.0.1:8126:1
#node 10.1.100.13:8126:1

$ statsd-proxy -v
[email protected]

gdb said it happens here.

$ sudo gdb /usr/bin/statsd-proxy core.3431
...Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000406178 in start (config=0xb40000ffff8f65ed, config@entry=0x2cd3e260) at src/statsd-proxy.c:108
108	        if ((ctxs[i] = ctx_new(config->nodes, config->num_nodes, config->port,

I'm not good at c program, so the best I can do is to add log_debug around and see the output.
Well, it doesn't help.
Any idea?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions