SIGSTOP is usually a debugging signal. That doesn't really look like a core dump, this just looks like normal debuggging to me. Are you sure this is the coredump ?
On Sunday, June 25, 2017 at 6:20:13 PM UTC-7, [email protected] wrote: > > > Hi experts, > > I meet a weird core dump when I try to build my grpc application using > asynchronous server. The call stack is as below > > gRPC(1.3.2) cpp build under MacOS. I completed build and install without > error. > > (lldb) bt > * thread #2, stop reason = signal SIGSTOP > * frame #0: 0x000000010d3756ab libgrpc++.dylib`grpc_pollset_size + 11 > frame #1: 0x000000010d38dbe2 > libgrpc++.dylib`grpc_completion_queue_create + 66 > frame #2: 0x000000010d3540d4 > libgrpc++.dylib`___lldb_unnamed_symbol68$$libgrpc++.dylib + 132 > frame #3: 0x000000010d35d61d > libgrpc++.dylib`grpc::ServerBuilder::AddCompletionQueue(bool) + 45 > > I tried grpc greeter cpp example, i got the same core dump as well. I > checked the registered, I have following information. > > (lldb) thread select 2 > * thread #2, stop reason = signal SIGSTOP > frame #0: 0x000000010d3756ab libgrpc++.dylib`grpc_pollset_size + 11 > libgrpc++.dylib`grpc_pollset_size: > -> 0x10d3756ab <+11>: movq (%rax), %rax > 0x10d3756ae <+14>: popq %rbp > 0x10d3756af <+15>: retq > > rax is 0 through lldb output. > > Can anyone give me some hints to diagnose and deal with this issue? I am > now completed stuck. > > Best, > > Yi > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/1b6e0791-851f-4225-a3c3-d5013c185b9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
