Segfault when using CLI #322

Open
opened 2022-12-22 14:46:14 +01:00 by Jef Roosens · 2 comments
$ vieter targets build 51 -remote
Creating base image...
signal 11: segmentation fault
addr2line: 'vieter': No such file
vieter(+0x120a86) [0x5598b2398a86]
addr2line: 'vieter': No such file
vieter(+0x374d2) [0x5598b22af4d2]
addr2line: 'vieter': No such file
vieter(+0xd91dc) [0x5598b23511dc]
addr2line: 'vieter': No such file
vieter(+0x122554) [0x5598b239a554]
addr2line: 'vieter': No such file
vieter(+0xdc124) [0x5598b2354124]
addr2line: 'vieter': No such file
vieter(+0x54e78) [0x5598b22cce78]
addr2line: 'vieter': No such file
vieter(+0x54d58) [0x5598b22ccd58]
addr2line: 'vieter': No such file
vieter(+0x54d58) [0x5598b22ccd58]
addr2line: 'vieter': No such file
vieter(+0xba778) [0x5598b2332778]
addr2line: 'vieter': No such file
vieter(+0x5096) [0x5598b227d096]
                                                        | 0x7f05e1172290 | /usr/lib/libc.so.6(+0x23290)
                                                        | 0x7f05e117234a | /usr/lib/libc.so.6(__libc_start_main+0x8a)
addr2line: 'vieter': No such file
vieter(+0x50e5) [0x5598b227d0e5]

No idea what could be causing this right now.

``` $ vieter targets build 51 -remote Creating base image... signal 11: segmentation fault addr2line: 'vieter': No such file vieter(+0x120a86) [0x5598b2398a86] addr2line: 'vieter': No such file vieter(+0x374d2) [0x5598b22af4d2] addr2line: 'vieter': No such file vieter(+0xd91dc) [0x5598b23511dc] addr2line: 'vieter': No such file vieter(+0x122554) [0x5598b239a554] addr2line: 'vieter': No such file vieter(+0xdc124) [0x5598b2354124] addr2line: 'vieter': No such file vieter(+0x54e78) [0x5598b22cce78] addr2line: 'vieter': No such file vieter(+0x54d58) [0x5598b22ccd58] addr2line: 'vieter': No such file vieter(+0x54d58) [0x5598b22ccd58] addr2line: 'vieter': No such file vieter(+0xba778) [0x5598b2332778] addr2line: 'vieter': No such file vieter(+0x5096) [0x5598b227d096] | 0x7f05e1172290 | /usr/lib/libc.so.6(+0x23290) | 0x7f05e117234a | /usr/lib/libc.so.6(__libc_start_main+0x8a) addr2line: 'vieter': No such file vieter(+0x50e5) [0x5598b227d0e5] ``` No idea what could be causing this right now.
Jef Roosens added the
bug
label 2022-12-22 14:46:14 +01:00

On further inspection, the error happened after the user tried to run a build after updating their kernel, without restarting. Apparently docker really doesn't like this, so it's possible the docker daemon returned an invalid response. This means the Vieter docker code probably assumes at some point that it's received valid output.

On further inspection, the error happened after the user tried to run a build after updating their kernel, without restarting. Apparently docker really doesn't like this, so it's possible the docker daemon returned an invalid response. This means the Vieter docker code probably assumes at some point that it's received valid output.

Pretty sure this bug has been fixed thanks to the recent docker code refactor, but until I can confirm this, I'll keep it open.

Pretty sure this bug has been fixed thanks to the recent docker code refactor, but until I can confirm this, I'll keep it open.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vieter-v/vieter#322
There is no content yet.