Skip to content

Conversation

evverx
Copy link
Contributor

@evverx evverx commented Aug 7, 2017

Fixes:

$ env -i valgrind --leak-check=full ./build/test-bus-chat
...
==7763== 1,888 (1,824 direct, 64 indirect) bytes in 1 blocks are
definitely lost in loss record 2 of 2
==7763==    at 0x4C2FA50: calloc (vg_replace_malloc.c:711)
==7763==    by 0x4F8FF9A: sd_bus_new (sd-bus.c:175)
==7763==    by 0x4F938BF: sd_bus_open_user (sd-bus.c:1138)
==7763==    by 0x109ACD: server_init (test-bus-chat.c:70)
==7763==    by 0x10BCF8: main (test-bus-chat.c:526)
==7763==

Closes #6481

Fixes:
```
$ env -i valgrind --leak-check=full ./build/test-bus-chat
...
==7763== 1,888 (1,824 direct, 64 indirect) bytes in 1 blocks are
definitely lost in loss record 2 of 2
==7763==    at 0x4C2FA50: calloc (vg_replace_malloc.c:711)
==7763==    by 0x4F8FF9A: sd_bus_new (sd-bus.c:175)
==7763==    by 0x4F938BF: sd_bus_open_user (sd-bus.c:1138)
==7763==    by 0x109ACD: server_init (test-bus-chat.c:70)
==7763==    by 0x10BCF8: main (test-bus-chat.c:526)
==7763==
```

Closes systemd#6481
@evverx evverx added the sd-bus label Aug 7, 2017
@evverx
Copy link
Contributor Author

evverx commented Aug 7, 2017

The CI failure has nothing to do with this PR. I'm trying to figure out what is going on in #6266 (comment).

@martinpitt
Copy link
Contributor

@evverx: see the console log. Seems it's some kind of ssh/networking failure. In PR #6556 it's the same, so I'll disable the centos test again.

@evverx
Copy link
Contributor Author

evverx commented Aug 7, 2017

@martinpitt, a network or ssh issue might have caused the failure, but that might also indicate the presence of some underlying problem as we have seen in #4456 (comment). Unfortunately, nothing meaningful can be done without the logs from the host.

@poettering poettering merged commit 4f6631c into systemd:master Aug 8, 2017
@evverx evverx deleted the sd-bus-ope-user-memleak branch August 9, 2017 04:14
andir pushed a commit to andir/systemd that referenced this pull request Sep 7, 2017
Fixes:
```
$ env -i valgrind --leak-check=full ./build/test-bus-chat
...
==7763== 1,888 (1,824 direct, 64 indirect) bytes in 1 blocks are
definitely lost in loss record 2 of 2
==7763==    at 0x4C2FA50: calloc (vg_replace_malloc.c:711)
==7763==    by 0x4F8FF9A: sd_bus_new (sd-bus.c:175)
==7763==    by 0x4F938BF: sd_bus_open_user (sd-bus.c:1138)
==7763==    by 0x109ACD: server_init (test-bus-chat.c:70)
==7763==    by 0x10BCF8: main (test-bus-chat.c:526)
==7763==
```

Closes systemd#6481
andir pushed a commit to andir/systemd that referenced this pull request Sep 22, 2017
Fixes:
```
$ env -i valgrind --leak-check=full ./build/test-bus-chat
...
==7763== 1,888 (1,824 direct, 64 indirect) bytes in 1 blocks are
definitely lost in loss record 2 of 2
==7763==    at 0x4C2FA50: calloc (vg_replace_malloc.c:711)
==7763==    by 0x4F8FF9A: sd_bus_new (sd-bus.c:175)
==7763==    by 0x4F938BF: sd_bus_open_user (sd-bus.c:1138)
==7763==    by 0x109ACD: server_init (test-bus-chat.c:70)
==7763==    by 0x10BCF8: main (test-bus-chat.c:526)
==7763==
```

Closes systemd#6481
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants