8000 wq segfaults on abort_workers · Issue #510 · cooperative-computing-lab/cctools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
wq segfaults on abort_workers #510
Closed
@btovar

Description

@btovar

Per Matthias:

Program received signal SIGSEGV, Segmentation fault.
0x00002b19fdba0980 in abort_slow_workers (q=0x7631f80) at work_queue.c:2566
2566 work_queue.c: No such file or directory.
in work_queue.c
(gdb) bt
#0 0x00002b19fdba0980 in abort_slow_workers (q=0x7631f80) at work_queue.c:2566
#1 0x00002b19fdba3836 in work_queue_wait_internal (q=0x7631f80, timeout=300, foreman_uplink=0x0,

foreman_uplink_active=0x0) at work_queue.c:3872

#2 0x00002b19fdba337a in work_queue_wait (q=0x7631f80, timeout=300) at work_queue.c:3673
#3 0x00002b19fdb93d02 in _wrap_work_queue_wait (self=, args=)

at work_queue_wrap.c:8581

...

This is the wq_wait segfault that we were recently discussing. fast_abort was enabled in the run.

Metadata

Metadata

Assignees

Labels

Work QueuebugFor modifications that fix a flaw in the code.critical

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0