https://bugs.kde.org/show_bug.cgi?id=474326
--- Comment #1 from Paul Floyd <pjfl...@wanadoo.fr> --- Looks like a GDB problem (gdb) target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-mcleak /jenkins/jobs/oi-userland/workspace/components/developer/gdb/gdb-13.2/gdbsupport/filestuff.cc:381: internal-error: gdb_socketpair_cloexec: socketpair not available on this host A problem internal to GDB has been detected, further debugging may prove unreliable. ----- Backtrace ----- 0x7b05c4 ??? 0xb6524c ??? 0xb65558 ??? 0xca19fc ??? 0xca2f46 ??? 0xa8e281 ??? 0xa8f6d2 ??? 0xa79a96 ??? 0xb153de ??? 0x7e472c ??? 0xb26158 ??? 0x8cc40b ??? 0x8cd8e8 ??? 0x8cce40 ??? 0xbaa251 ??? 0x8cbd9d ??? 0x8ccc54 ??? 0x8cb849 ??? 0xca2105 ??? 0xca27f2 ??? 0x987bf1 ??? 0x989594 ??? 0x70a596 ??? 0x70a4a6 ??? 0x70a407 ??? --------------------- /jenkins/jobs/oi-userland/workspace/components/developer/gdb/gdb-13.2/gdbsupport/filestuff.cc:381: internal-error: gdb_socketpair_cloexec: socketpair not available on this host A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) I'll log an issue with the illumos bugtracker, but that's usually pretty hopeless. -- You are receiving this mail because: You are watching all bug changes.