From: Richard Hodges (hodges.r_at_[hidden])
Date: 2020-10-14 07:43:23
There's not a lot of information to go on here. It looks as if you might
have a segfault in the scheduler rather than the timer itself. Is the
io_context still in scope?
Happy to chat in real time on slack if you have access to it. I generally
hang out in the #beast channel as I maintain this library.
On Wed, 14 Oct 2020 at 02:30, Jupiter via Boost <boost_at_[hidden]>
> My application is running one thread under boost::asio::io_service, it
> is an embedded system running on an ARM processor with Linux, so no
> gdb installed. The application is also using a
> boost::asio::deadline_timer to call a function every second, but I got
> following segmentation stack trace:
> I thought I could run c++filt to demangling the library name, not sure
> why it didn't demangle the name today.
> I used the same boost::asio::deadline_timer version 1.69 for another
> application running on Ubuntu which was working fine, what I could be
> Thank you.
> Kind regards,
> Unsubscribe & other changes:
-- Richard Hodges hodges.r_at_[hidden] office: +442032898513 home: +376841522 mobile: +376380212
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk