[Bug build/25268] New: Build broken on macOS at 4da8c3a8a (Oct 13, 2019), which introduced pthread_setname_np()

wataash at wataash dot com sourceware-bugzilla@sourceware.org
Tue Dec 10 11:29:00 GMT 2019


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

            Bug ID: 25268
           Summary: Build broken on macOS at 4da8c3a8a (Oct 13, 2019),
                    which introduced pthread_setname_np()
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: wataash at wataash dot com
                CC: tromey at sourceware dot org
  Target Milestone: ---

On macOS the signature of pthread_setname_np() is:
    void pthread_setname_np(const char *name); 
, which is not what the commit 4da8c3a8a assumes:

      CXX    gdbsupport/thread-pool.o
    ../../gdb/gdbsupport/thread-pool.c:79:4: error: no matching function for
call to 'pthread_setname_np'
              pthread_setname_np (thread.native_handle (), "gdb worker");
              ^~~~~~~~~~~~~~~~~~
    /usr/include/pthread.h:513:5: note: candidate function not viable: requires
1 argument, but 2 were provided
    int     pthread_setname_np(const char*);
            ^
    1 error generated.Build broken on macOS at 4da8c3a8a (Oct 13, 2019), which
introduced pthread_setname_np()

On macOS the signature of pthread_setname_np() is:
    void pthread_setname_np(const char *name); 
, which is not what the commit 4da8c3a8a assumes:

      CXX    gdbsupport/thread-pool.o
    ../../gdb/gdbsupport/thread-pool.c:79:4: error: no matching function for
call to 'pthread_setname_np'
              pthread_setname_np (thread.native_handle (), "gdb worker");
              ^~~~~~~~~~~~~~~~~~
    /usr/include/pthread.h:513:5: note: candidate function not viable: requires
1 argument, but 2 were provided
    int     pthread_setname_np(const char*);
            ^
    1 error generated.

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


More information about the Gdb-prs mailing list