On Fri, 2014-11-28 at 11:37 +, Ian Campbell wrote:
On Thu, 2014-11-27 at 12:34 +, Andrew Cooper wrote:
The error handling from a failed memory allocation should return
PyErr_SetFromErrno(xc_error_obj); rather than simply calling it and
continuing
to the memcpy() below, with the
On 09/12/14 14:27, Ian Campbell wrote:
On Fri, 2014-11-28 at 11:37 +, Ian Campbell wrote:
On Thu, 2014-11-27 at 12:34 +, Andrew Cooper wrote:
The error handling from a failed memory allocation should return
PyErr_SetFromErrno(xc_error_obj); rather than simply calling it and
On Tue, Dec 09, 2014 at 02:30:24PM +, Andrew Cooper wrote:
On 09/12/14 14:27, Ian Campbell wrote:
On Fri, 2014-11-28 at 11:37 +, Ian Campbell wrote:
On Thu, 2014-11-27 at 12:34 +, Andrew Cooper wrote:
The error handling from a failed memory allocation should return
On Thu, 2014-11-27 at 12:34 +, Andrew Cooper wrote:
The error handling from a failed memory allocation should return
PyErr_SetFromErrno(xc_error_obj); rather than simply calling it and continuing
to the memcpy() below, with the dest pointer being NULL.
Furthermore, the context string is
On Fri, 2014-11-28 at 11:47 +, Andrew Cooper wrote:
On 28/11/14 11:37, Ian Campbell wrote:
On Thu, 2014-11-27 at 12:34 +, Andrew Cooper wrote:
The error handling from a failed memory allocation should return
PyErr_SetFromErrno(xc_error_obj); rather than simply calling it and
The error handling from a failed memory allocation should return
PyErr_SetFromErrno(xc_error_obj); rather than simply calling it and continuing
to the memcpy() below, with the dest pointer being NULL.
Furthermore, the context string is simply an input parameter to the hypercall,
and is not
