search for: cb_fn

...at res_pjsip_session.c:5567 #3 0x00007f773801965d in nat_invoke_hook (obj=<optimized out>, arg=arg at entry=0x7f772c1a0a50, flags=flags at entry=0) at res_pjsip_nat.c:299 #4 0x000055e7c09218c0 in internal_ao2_traverse (self=self at entry=0x7f774014cc18, flags=flags at entry=OBJ_SEARCH_NONE, cb_fn=cb_fn at entry=0x7f7738019640 <nat_invoke_hook>, arg=arg at entry=0x7f772c1a0a50, tag=tag at entry=0x0, file=file at entry=0x7f773801b009 "res_pjsip_nat.c", line=<optimized out>, func=<optimized out>, type=AO2_CALLBACK_DEFAULT, data=0x0) at astobj2_container.c:328 #5...

...at res_pjsip_session.c:5567 #3 0x00007f773801965d in nat_invoke_hook (obj=<optimized out>, arg=arg at entry=0x7f772c1a0a50, flags=flags at entry=0) at res_pjsip_nat.c:299 #4 0x000055e7c09218c0 in internal_ao2_traverse (self=self at entry=0x7f774014cc18, flags=flags at entry=OBJ_SEARCH_NONE, cb_fn=cb_fn at entry=0x7f7738019640 <nat_invoke_hook>, arg=arg at entry=0x7f772c1a0a50, tag=tag at entry=0x0, file=file at entry=0x7f773801b009 "res_pjsip_nat.c", line=<optimized out>, func=<optimized out>, type=AO2_CALLBACK_DEFAULT, data=0x0) at astobj2_container.c:328 #5...

On Wed, Aug 9, 2023 at 3:20 PM Dan Cropp <dcropp at amtelco.com> wrote: > I have a customer who just encountered a crash while running Asterisk > 18.17.1 version. > > > > I’m trying to adapt to the changes so not sure where best to look or how > to possibly report this. > > > > I started by going through >

...(dialogobj=<value optimized out>, arg=<value optimized out>, flags=<value optimized out>) at chan_sip.c:19564 dialog = (struct sip_pvt *) 0x2aab18b892d8 __PRETTY_FUNCTION__ = "dialog_needdestroy" #8 0x000000000044736e in internal_ao2_callback (c=0x1346c4c8, flags=6, cb_fn=0x2aaaceac2d70, arg=0x0, data=0x0, type=DEFAULT, tag=0x0, file=0x0, line=0, func=0x0) at astobj2.c:1102 match = -827576976 __list_head = (struct bucket *) 0x1346c4e8 __list_next = (struct bucket_entry *) 0x0 __list_prev = (struct bucket_entry *) 0x0 __list_current = <value optimized out>...

...aque, e.g., calls from host go through a driver API, I doubt there is really a problem. I imagine it somehow like OpenMP looks, here my conceptual model: --- // Host static char KERNEL_ID; void offload(void *payload) {   driver_invoke_kernel(&KERNEL_ID, payload); } __attribute__((callback (cb_fn, arg))) void driver_invoke_kernel(void(*cb_fn)(void *), void *arg); // Device device 1 global alias KERNEL_ID = kernel;     // "LLVM-IR-like syntax" device 1 void kernel(void *payload) {    auto *typed_payload = static_cast<...>(payload);    ... } --- The "important"...

...ome/stuff/software This is the end portion of what I get (note that the 'debug[1,2]' lines are generated by ssh): ... recv_files finished wrote 16 bytes read 154748 bytes 9984.77 bytes/sec total size is 10142392 speedup is 65.53 debug1: channel: 0 rcvd request for exit-status debug1: cb_fn 2677c cb_event 91 debug1: channel 0: write failed debug1: channel 0: output open->closed debug1: channel 0: close_write debug1: channel 0: rcvd eof debug1: channel 0: rcvd close debug1: channel 0: input open->closed debug1: channel 0: close_read debug1: channel 0: send close debug1: channel 0...

On 7/28/20 2:24 PM, Renato Golin wrote: > On Tue, 28 Jul 2020 at 20:07, Johannes Doerfert via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Long story short, I think host & device need to, and in practice do, >> agree on the data layout of the address space they use to communicate. > > You can design APIs that call functions into external hardware that

http://bass.directhit.com/openssh_snap/ Starting tonight I plan on tracking changes very closely with the OpenBSD tree. I need people to test the latest snapshot (9/14 at of right now) and report success or failure on compiling. I am starting this now because we are looking at a code freeze soon and I really want to ensure it compiles and runs on all existing platforms. So we (the portable