-
Notifications
You must be signed in to change notification settings - Fork 562
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
cmd/{snap-confine,libsnap-confine-private,snap-shutdown}: cleanup low-level C bits #4153
Changes from all commits
c3f581a
c6ceaeb
1e407d3
668b676
70d6c93
fd8f5fb
706a213
597029b
b6d40fc
2ed4577
efd8081
59cfa18
5e34947
f352040
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -33,7 +33,7 @@ static bool broken_alter_msg(struct sc_fault_state *state, void *ptr) | |
return true; | ||
} | ||
|
||
static void test_fault_injection() | ||
static void test_fault_injection(void) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I dislike that this needs to be done :/ That is one of my complains about C (one of many ;) - the fact that K&R C from ~1879 requires us to nowdays write clunky (void) like this. Oh well. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I guess you meant 1978, although it does feel like 19th century by modern standards :) |
||
{ | ||
g_assert_false(sc_faulty("foo", NULL)); | ||
|
||
|
@@ -57,7 +57,7 @@ static void test_fault_injection() | |
sc_reset_faults(); | ||
} | ||
|
||
static void __attribute__ ((constructor)) init() | ||
static void __attribute__ ((constructor)) init(void) | ||
{ | ||
g_test_add_func("/fault-injection", test_fault_injection); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gentoo has a policy where those are not added automatically as they tend to break good builds due to new compiler releases. I was wondering if those flags should not be in the unit tests, and instead we could resort to perhaps, just, -Wall
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, do you know if they push
-Werror
by default? Just having the warnings enabled should not cause build failures.