Skip to content

Segmentation fault on using consumer #167

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tejas3190 opened this issue Apr 2, 2017 · 3 comments
Closed

Segmentation fault on using consumer #167

tejas3190 opened this issue Apr 2, 2017 · 3 comments

Comments

@tejas3190
Copy link

warning: core file may not match specified executable file.
[New LWP 8720]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `python logger.py'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 rd_kafka_commit (rk=0x0, offsets=offsets@entry=0x0, async=async@entry=1) at rdkafka_offset.c:420
420 if (!(rkcg = rd_kafka_cgrp_get(rk)))
(gdb) bt
#0 rd_kafka_commit (rk=0x0, offsets=offsets@entry=0x0, async=async@entry=1) at rdkafka_offset.c:420
#1 0x00007fd879fabb66 in Consumer_commit (self=0x7fd8796e2328, args=, kwargs=) at confluent_kafka/src/Consumer.c:270
#2 0x000000000049ec76 in PyEval_EvalFrameEx ()
#3 0x0000000000499ef2 in PyEval_EvalFrameEx ()
#4 0x0000000000499ef2 in PyEval_EvalFrameEx ()
#5 0x00000000004a1634 in ?? ()
#6 0x000000000044e4a5 in PyRun_FileExFlags ()
#7 0x000000000044ec9f in PyRun_SimpleFileExFlags ()
#8 0x000000000044f904 in Py_Main ()
#9 0x00007fd87b687ec5 in __libc_start_main (main=0x44f9c2

, argc=2, argv=0x7fffc89bf758, init=, fini=, rtld_fini=,
stack_end=0x7fffc89bf748) at libc-start.c:287
#10 0x0000000000578c4e in _start ()
(gdb) f 0
#0 rd_kafka_commit (rk=0x0, offsets=offsets@entry=0x0, async=async@entry=1) at rdkafka_offset.c:420
420 if (!(rkcg = rd_kafka_cgrp_get(rk)))
(gdb)

@tejas3190 tejas3190 changed the title Segmentation fault on calling commit Segmentation fault on using consumer Apr 2, 2017
@edenhill
Copy link
Contributor

edenhill commented Apr 9, 2017

@tejas3190 Why did you close this issue?

@tejas3190
Copy link
Author

tejas3190 commented Apr 9, 2017

Well i just thought the implementation that i was trying was wrong. I had a signal handler in which i tried to close the consumer connection which is leading to crash. Any call to consumer api (in confluent - python) leads to crash when called from signal handler.

@edenhill
Copy link
Contributor

Okay, yeah, that makes sense. Signal handlers are inherently unsafe on Unix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants