`port rev-upgrade` exits with code 139

Rainer Müller raimue at macports.org
Mon Nov 9 02:39:27 PST 2015

On 2015-11-09 10:34, René J.V. Bertin wrote:
> However, port now exits with code 139 each time it terminates with
> the rev-upgrade phase, and there is no debug output whatsoever to
> determine why.

Exit code 139 is usually how a shell tells you the command died with
signal 11, which is SIGSEGV (Segmentation Fault). The process made an
invalid memory access and is terminated abruptly.

This could be caused by your modifications in Pextlib or an actual bug
in the base code that just never triggers on OS X. You would have to
obtain a core file to examine this in a debugger.


More information about the macports-dev mailing list