Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
L
libzmq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
libzmq
Commits
f0d97e02
Unverified
Commit
f0d97e02
authored
Jan 15, 2019
by
Doron Somech
Committed by
GitHub
Jan 15, 2019
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #3363 from bluca/tests_race_conditions
Problem: GCC warnings about string overflows in tests
parents
87dbd39a
4d385524
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
3 additions
and
2 deletions
+3
-2
test_inproc_connect.cpp
tests/test_inproc_connect.cpp
+1
-1
test_issue_566.cpp
tests/test_issue_566.cpp
+2
-1
No files found.
tests/test_inproc_connect.cpp
View file @
f0d97e02
...
...
@@ -160,7 +160,7 @@ void test_connect_before_bind_ctx_term ()
// Connect first
void
*
connect_socket
=
test_context_socket
(
ZMQ_ROUTER
);
char
ep
[
20
];
char
ep
[
32
];
sprintf
(
ep
,
"inproc://cbbrr%d"
,
i
);
TEST_ASSERT_SUCCESS_ERRNO
(
zmq_connect
(
connect_socket
,
ep
));
...
...
tests/test_issue_566.cpp
View file @
f0d97e02
...
...
@@ -66,7 +66,8 @@ void test_issue_566 ()
// Create dealer with unique explicit routing id
// We assume the router learns this out-of-band
void
*
dealer
=
zmq_socket
(
ctx2
,
ZMQ_DEALER
);
char
routing_id
[
10
];
// Leave space for NULL char from sprintf, gcc warning
char
routing_id
[
11
];
sprintf
(
routing_id
,
"%09d"
,
cycle
);
TEST_ASSERT_SUCCESS_ERRNO
(
zmq_setsockopt
(
dealer
,
ZMQ_ROUTING_ID
,
routing_id
,
10
));
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment