Builder curl-unthreaded-solaris11-sparc Build #6179

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-curl-unthreaded-solaris11-sparc' triggered this build

Steps and Logfiles:

1. git update ( 11 secs )
   1. stdio
2. Runtest './tests/testcurl.pl --nogitpull ...' ( 23 mins, 20 secs )
   1. stdio
   2. resultlog
3. Mail result 'cat resultlog ...' ( 0 secs )
   1. stdio

Build Properties:

Forced Build Properties:

Responsible Users:

1. Viktor Szakats

   commitohnoyoudont@vsz.me

Timing:

All Changes:

:

1. Change #277244

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Thu 06 Aug 2026 12:48:45
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	3aae64e4fbee7c1fa408c54df18d3f631781c283

   Comments

   servers: drop complex and redundant signal handler output
   In year 2020 the Unixy signal handler received a `logmsg()` call to log
   the signal number, but at the same time it already saved it to a global
   variable and logged it on exit, meaning this extra `logmsg()` was
   redundant. Because `logmsg()` is not signal-safe, this call was replaced
   in 2025 with signal-safe logging, but without the signal number, while
   also adding complexity, spent on trying to open the log file and handle
   errors. All for nothing, because the signal number was logged all along.
   
   This patch removes all this, and simplifies it to a single, signal-safe
   `write()` to STDERR to say that the signal handler triggered. This is
   also non-critical, but may help debugging.
   
   Also: point the POSIX documentation to the 2004 revision, which has a
   shorter list of safe functions. (was: 2018)
   
   Follow-up to e95f509c66abdd88ae02e3243cdc217f19c4a330 #16852
   Follow-up to 9869f6dc5af85caf2e0fd4c56713a7f2049ecfff #5218
   
   Closes #22507

   Changed files

   • tests/server/util.c