Builder libpcap-solaris10-sparcv9 Build #3293

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-libpcap-solaris10-sparcv9' triggered this build

Steps and Logfiles:

1. git update ( 18 secs )
   1. stdio
2. shell Set developer mode ( 0 secs )
   1. stdio
3. shell_1 './autogen.sh' ( 21 secs )
   1. stdio
4. shell_2 './configure' ( 1 mins, 3 secs )
   1. stdio
   2. config.log
5. shell_3 'gmake' ( 54 secs )
   1. stdio
6. shell_4 'gmake check' ( 18 mins, 30 secs )
   1. stdio
7. shell_5 'rm -rf ...' ( 0 secs )
   1. stdio
8. shell_6 'gmake install ...' ( 3 secs )
   1. stdio
9. trigger triggered trigger-tcpdump-solaris10-sparcv9 ( 13 mins, 36 secs )
   1. - no logs -
   2. tcpdump-solaris10-sparcv9 #6209

Build Properties:

Forced Build Properties:

Responsible Users:

1. Guy Harris

   gharrisohnoyoudont@sonic.net

Timing:

All Changes:

:

1. Change #261228

   Category	libpcap
   Changed by	Guy Harris <gharrisohnoyoudont@sonic.net>
   Changed at	Mon 16 Mar 2026 20:52:21
   Repository	https://git.tcpdump.org/libpcap
   Project	libpcap
   Branch	master
   Revision	95ae2182d46efa1480a53ca934e659b31deb1f71

   Comments

   rdmasniff: clean up some resource freeing issues.
   Add a routine rdmasniff_free_resoources() to free up all resources
   pointed to by the struct pcap_rdmasniff structure for an open device.
   Use it both when closing a pcap_t and when cleaning up after a failed
   attempt to activate a pcap_t.
   
   Free those routines in the order specified in issue #1532.
   
   Don't save the struct ibv_device * found in pcap_create(); we free up
   the  ibv_device array allocated by ibv_get_device_list() when we return
   from rdmasniff_create(), and that invalidates the entries in that array.
   See the ibv_get_device_list() documentation, and issue #1300.
   
   Fixes #1532.
   
   Fixes #1300.
   
   Improve checking for ibv_ error returns and messages for those errors.
   
   Improve handling of the port number - don't fetch or check it in the
   create routine, so that an invalid port number doesn't prevent the
   underlying device from being recognized as a valid RDMA device, but do
   fetch and check it in the activate routine, so we can report the error
   to the user.

   Changed files

   • CHANGES
   • pcap-rdmasniff.c