Skip to content
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.

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

Segfault on new client connect #1

Open
tehcyx opened this issue Dec 27, 2017 · 0 comments
Open

Segfault on new client connect #1

tehcyx opened this issue Dec 27, 2017 · 0 comments
Assignees
Labels
Milestone

Comments

@tehcyx
Copy link
Owner

tehcyx commented Dec 27, 2017

There's a segfault in client.c line 163 on the strncopy that I found by using gdb:

[New Thread 0x7f93a2d20700 (LWP 17294)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f93a3530700 (LWP 17293)]
__strncpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:1672
1672    ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S: No such file or directory.
(gdb) backtrace
#0  __strncpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:1672
#1  0x0000000000402d12 in client_read_socket (socket=4, buffer=0x7f93a352fd00 "", err=0x7f93a352fae2) at src/client.c:163
#2  0x00000000004026e9 in client_connect (new_client=0x0) at src/client.c:34
#3  0x0000000000000000 in ?? ()	

Reproduce with:

  1. Connect client (sometimes happens here already)
  2. If your client supports it use 'reconnect' functionality (have always gotten segfault here now)
@tehcyx tehcyx added the bug label Dec 27, 2017
@tehcyx tehcyx added this to the 0.1 milestone Dec 27, 2017
@tehcyx tehcyx self-assigned this Dec 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant