[Bug gdb/19397] New: internal-error: creating event pipe failed on softfloat mipsel O32 with uclibc-ng-1.0.9 & gcc-5.2.0

["opotapenko at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19397

            Bug ID: 19397
           Summary: internal-error: creating event pipe failed on
                    softfloat mipsel O32 with uclibc-ng-1.0.9 & gcc-5.2.0
           Product: gdb
           Version: 7.10
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: opotapenko at gmail dot com
  Target Milestone: ---

Whenever trying to use gdb on O32 mipsel uclibc-ng platform that was
cross-compiled with the use of gcc-5.2.0, I get this error:

root@unknown:/tmp/home/root# gdb php
GNU gdb (GDB) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mipsel-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from php...(no debugging symbols found)...done.
(gdb) run -v
Starting program: /opt/bin/php -v
linux-nat.c:4715: internal-error: creating event pipe failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

This is a bug, please report it.  For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

linux-nat.c:4715: internal-error: creating event pipe failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Unable to dump core, use `ulimit -c unlimited' before executing GDB next time.
Command aborted.
(gdb)

Unfortunately, I cannot provide a core dump, since my platform (mipsel router)
doesn't seem to support core dump creation (after issuing `ulimit -c unlimited`
a core dump is nowhere to be found).

The same issue happened with gdb 7.8.1.

This may be platform-specific, since gdb works fine on armv7 platform of
similar setup, built with tools of similar configs.

-- 
You are receiving this mail because:
You are on the CC list for the bug.