On Wed, 10 Sep 2008 20:01:21 -0000, Andy Spitzer wrote:
} Among the major issues with Solaris is that Sun's vsprintf (and all the
} *printfs that end up using it) will core dump if a NULL string is
} printed with the %s format. As Linux (well glibc) will instead print
} "(nil)" in that case, much of the code in sipX relied on the glibc
} behavior, especially in debug code where the whole point was to see
} if the string was null or not!
I definetly agree with the Sun folks on this one, trying to print a
NULL pointer is a bug. However you don't need to argue the philosophy
behind it. The fact is the current behaviour is not portable but instead
relies on a (mis)feature of glibc.
} It would thus require replacing ALL the *printf functions to get the
} desired behavior, and that turned out to be too large a task.
My question is if someone does the work will the patches be accepted?
} Sun's take now seems to be "run Linux in an xVM container" instead
} of porting.
That doesn't help with the CoolThreads servers. In that environment
(mine) you'd need to run a Logical Domain (LDOM) with a SPARC64 linux
kernel in it. Given that it's a bare metal hypervisor on a chip
multithreading system that might be a workable environment.
Has anyone ported to a SPARC64 linux?
} As a Solaris enthusiast, I would love to see sipX running natively. I
} don't think replacing all %s arguments with a macro is the right answer
} however, as new code will certainly forget to do this, and it swells the
} code size and considerably. I'd love to find a "fix it in one place"
} type of solution, but it hasn't happend yet.
A quick fix isn't the right answer. If the project is to be portable
than it has to be coded for portability. Is the team ready to accept
that?
-Vance
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
