Doing 'ps' on the target shows: 2592 root 2592 S /usr/bin/dbus-daemon --fork --print-pid 6 --print-add 2600 root 2592 S /usr/bin/dbus-daemon --fork --print-pid 6 --print-add 2625 root 2592 S /usr/bin/dbus-daemon --fork --print-pid 6 --print-add 2638 root 2592 S /usr/bin/dbus-daemon --fork --print-pid 6 --print-add 2647 root SW [pdflush] 2654 root 2592 S /usr/bin/dbus-daemon --fork --print-pid 6 --print-add What's this for and is there some way to get rid of it, or at least clean up when the GDB server quits?
Need to investigate the route of this issue and ensure that we clean up properly after each debug session.
Hi, Josh Do you know how to reproduce this bug. Here I tried many times, and when ps, got below output. I did not have many /bin/dbus-daemon --fork process. Thanks & Regards, criping 102 1044 1 0 07:37 ? 00:00:00 dbus-daemon --system --fork gdm 1625 1 0 07:37 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session lke 2035 1991 0 07:39 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session gnome-session lke 2038 1 0 07:39 ? 00:00:00 /bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session lke 2039 1 0 07:39 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session gnome-session root 3924 2499 0 08:08 pts/3 00:00:00 grep dbus
I don't have any further reproduction information other than what Gary has provided. Gary, are you still seeing this issue?
We can't reproduce the bug so far. And get no response from bug reporter. Thanks& Regards, criping
Can't reproduce and the original reporter no further comment once contacted