This is an automated email from the ASF dual-hosted git repository.

guangmingchen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brpc.git


The following commit(s) were added to refs/heads/master by this push:
     new aa784b83 fix: remove references to non-existent tracked_objects.h in 
platform_thread_freebsd.cc (#3223)
aa784b83 is described below

commit aa784b830824ca41d22b97d69e9692ab522dcd48
Author: Daniel Morante <[email protected]>
AuthorDate: Mon Feb 23 01:52:56 2026 -0600

    fix: remove references to non-existent tracked_objects.h in 
platform_thread_freebsd.cc (#3223)
    
    The tracked_objects.h header and ThreadData::InitializeThreadContext()
    were part of Chromium's base library profiling subsystem, which was
    never ported to brpc. The Linux (platform_thread_linux.cc) and macOS
    (platform_thread_mac.mm) equivalents already had these references
    removed. This causes a compile error on FreeBSD:
    
      fatal error: 'butil/tracked_objects.h' file not found
---
 src/butil/threading/platform_thread_freebsd.cc | 2 --
 1 file changed, 2 deletions(-)

diff --git a/src/butil/threading/platform_thread_freebsd.cc 
b/src/butil/threading/platform_thread_freebsd.cc
index a18264be..ad5fa949 100644
--- a/src/butil/threading/platform_thread_freebsd.cc
+++ b/src/butil/threading/platform_thread_freebsd.cc
@@ -13,7 +13,6 @@
 #include "butil/safe_strerror_posix.h"
 #include "butil/threading/thread_id_name_manager.h"
 #include "butil/threading/thread_restrictions.h"
-#include "butil/tracked_objects.h"
 
 #if !defined(OS_NACL)
 #include <sys/resource.h>
@@ -46,7 +45,6 @@ int ThreadNiceValue(ThreadPriority priority) {
 // static
 void PlatformThread::SetName(const char* name) {
   ThreadIdNameManager::GetInstance()->SetName(CurrentId(), name);
-  tracked_objects::ThreadData::InitializeThreadContext(name);
 
   SetNameSimple(name);
 }


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to