[MacPorts] #50350: rsync crashes: malloc error: "pointer being freed was not allocated"

[MacPorts]

#50350: rsync crashes: malloc error: "pointer being freed was not allocated"
------------------------+--------------------------------
  Reporter:  Polyergic  |      Owner:  macports-tickets@…
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.3.4
Resolution:             |   Keywords:
      Port:  rsync      |
------------------------+--------------------------------

Comment (by kencu):

 That error:
 {{{
 malloc: *** error for object 0x7fa300600070: pointer being freed was not
 allocated
 *** set a breakpoint in malloc_error_break to debug
 }}}
 is the exact error you see when there is a ABI mixup between the system
 libstdc++ and macports libstdc++ when using libgcc.

 My (incomplete) understanding of why this error occurs is that an object
 is created by one of the libraries, held by the application for some
 period of time I presume, and then passed off to the other library to
 release. But the ABI issue makes the release fail.

 Whether that applies in this case, I can't be sure.

-- 
Ticket URL: <https://trac.macports.org/ticket/50350#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS