The nix library does a good job of providing idiomatic rust wrappers around low-level UNIX operations, including sending and handling signals. In this case, you would create a nix::Pid from child_process.id(), then pass it to kill like so: use nix::unistd::Pid; use nix::sys::signal::{self, Signal}; // Spawn child process. let mut child = std::process::Command::new(); /* build rest … Read more
As mentioned bulk_create does not trigger these signals – https://docs.djangoproject.com/en/1.8/ref/models/querysets/#bulk-create This method inserts the provided list of objects into the database in an efficient manner (generally only 1 query, no matter how many objects there are). This has a number of caveats though: The model’s save() method will not be called, and the pre_save and … Read more
You can use os.kill(): os.kill(os.getpid(), signal.SIGUSR1) Put this anywhere in your code that you want to send the signal from.
The usual way is to set an atomic flag (like std::atomic<bool>) which is checked by all threads (including the main thread). If set, then the sub-threads exit, and the main thread starts to join the sub-threads. Then you can exit cleanly. If you use std::thread for the threads, that’s a possible reason for the crashes … Read more
Yes. See the documentation: from django.db.models.signals import post_save instance = MyModel(field=’qwerty’) post_save.send(MyModel, instance=instance, created=True)
Use signal handlers: import asyncio from signal import SIGINT, SIGTERM async def main_coro(): try: await awaitable() except asyncio.CancelledError: do_cleanup() if __name__ == “__main__”: loop = asyncio.get_event_loop() main_task = asyncio.ensure_future(main_coro()) for signal in [SIGINT, SIGTERM]: loop.add_signal_handler(signal, main_task.cancel) try: loop.run_until_complete(main_task) finally: loop.close()
I’ll bet that xmms2d is using sigwait() to handle signals, which breaks gdb’s ability to catch CTRL-C. See https://bugzilla.kernel.org/show_bug.cgi?id=9039 I got an idea for a workaround by reading Continue to debug after failed assertion on Linux? — when I’m ready to break in gdb, I run “kill -TRAP <pid>” from another terminal window.
This is an error that I have mostly seen on 64 bit iOS devices and can happen if multiple threads read and change a variable under ARC. For example, I fixed a crash today where multiple background threads were reading and using a static NSDate and NSString variable and updating them without doing any kind … Read more
I think that bind makes it easier to create slots (cfr. the ‘preferred’ syntax vs. the ‘portable’ syntax – that’s all going away). The observer management, however, is not becoming less complex. But as @R. Martinho Fernandes mentions: an std::vector<std::function< r(a1) > > is now easily created without the hassle for an (artificial) ‘pure virtual’ … Read more
No. From the man pages: execve() does not return on success, and the text, data, bss, and stack of the calling process are overwritten by that of the program loaded. The program invoked inherits the calling process’s PID, and any open file descriptors that are not set to close on exec. Signals pending on the … Read more