mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-02-22 22:45:27 +01:00
Code Issues Projects Releases Wiki Activity
core-lightning/common/subdaemon.h

14 lines
342 B
C
Raw Normal View History

subdaemon.c: subdaemon_setup() routine for all daemons. Our handling of SIGPIPE was incoherent and inconsistent, and we had much cut & paste between the daemons. They should *ALL* ignore SIGPIPE, and much of the rest of the boilerplate can be shared, so should be. Reported-by: @ZmnSCPxj Fixes: #528 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-01-08 20:31:09 +10:30
#ifndef LIGHTNING_COMMON_SUBDAEMON_H
#define LIGHTNING_COMMON_SUBDAEMON_H
#include "config.h"
common/daemon: common routines for all daemons. In particular, the main daemon and subdaemons share the backtrace code, with hooks for logging. The daemon hook inserts the io_poll override, which means we no longer need io_debug.[ch]. Though most daemons don't need it, they still link against ccan/io, so it's harmess (suggested by @ZmnSCPxj). This was tested manually to make sure we get backtraces still. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-03-29 12:36:45 +10:30
#include <common/daemon.h>
common: reduce header differences for DEVELOPER vs non-DEVELOPER. `make update-mocks` is usually run in DEVELOPER mode, but then it includes definitions for functions which aren't declared in non-DEVELOPER mode. We hacked this in a few places, but it's fragile, and worst, now we have EXPERIMENTAL_FEATURES as well, it's complex. Instead, declare developer-only functions (but don't define them). This is a bit more awkward if you accidentally use one in non-DEVELOPER code (link error rather than compile error), but makes autogenerating test mocks much easier. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-06 14:10:05 +09:30
struct htable;
subdaemon.c: subdaemon_setup() routine for all daemons. Our handling of SIGPIPE was incoherent and inconsistent, and we had much cut & paste between the daemons. They should *ALL* ignore SIGPIPE, and much of the rest of the boilerplate can be shared, so should be. Reported-by: @ZmnSCPxj Fixes: #528 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-01-08 20:31:09 +10:30
common/daemon: common routines for all daemons. In particular, the main daemon and subdaemons share the backtrace code, with hooks for logging. The daemon hook inserts the io_poll override, which means we no longer need io_debug.[ch]. Though most daemons don't need it, they still link against ccan/io, so it's harmess (suggested by @ZmnSCPxj). This was tested manually to make sure we get backtraces still. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-03-29 12:36:45 +10:30
/* daemon_setup, but for subdaemons */
subdaemon.c: subdaemon_setup() routine for all daemons. Our handling of SIGPIPE was incoherent and inconsistent, and we had much cut & paste between the daemons. They should *ALL* ignore SIGPIPE, and much of the rest of the boilerplate can be shared, so should be. Reported-by: @ZmnSCPxj Fixes: #528 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-01-08 20:31:09 +10:30
void subdaemon_setup(int argc, char *argv[]);
common: reduce header differences for DEVELOPER vs non-DEVELOPER. `make update-mocks` is usually run in DEVELOPER mode, but then it includes definitions for functions which aren't declared in non-DEVELOPER mode. We hacked this in a few places, but it's fragile, and worst, now we have EXPERIMENTAL_FEATURES as well, it's complex. Instead, declare developer-only functions (but don't define them). This is a bit more awkward if you accidentally use one in non-DEVELOPER code (link error rather than compile error), but makes autogenerating test mocks much easier. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-06 14:10:05 +09:30
/* Only defined if DEVELOPER */
common/subdaemon: helpers for dumping memleaks in subdaemons. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-11-22 08:16:37 +10:30
bool dump_memleak(struct htable *memtable);
subdaemon.c: subdaemon_setup() routine for all daemons. Our handling of SIGPIPE was incoherent and inconsistent, and we had much cut & paste between the daemons. They should *ALL* ignore SIGPIPE, and much of the rest of the boilerplate can be shared, so should be. Reported-by: @ZmnSCPxj Fixes: #528 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-01-08 20:31:09 +10:30
#endif /* LIGHTNING_COMMON_SUBDAEMON_H */
Reference in a new issue Copy permalink