On Tue, Jun 24, 2014 at 9:46 AM, Gurucharan Shetty wrote:
> On Mon, Jun 23, 2014 at 11:51 AM, Ben Pfaff wrote:
>> On Fri, Jun 13, 2014 at 07:40:02AM -0700, Gurucharan Shetty wrote:
>>> There is no 'kill -l' type functionality available on Windows.
>>> So instead of looking for the string 'ABRT',
On Mon, Jun 23, 2014 at 11:51 AM, Ben Pfaff wrote:
> On Fri, Jun 13, 2014 at 07:40:02AM -0700, Gurucharan Shetty wrote:
>> There is no 'kill -l' type functionality available on Windows.
>> So instead of looking for the string 'ABRT', check for the exit
>> code in both platforms. On msys (unit test
On Fri, Jun 13, 2014 at 07:40:02AM -0700, Gurucharan Shetty wrote:
> There is no 'kill -l' type functionality available on Windows.
> So instead of looking for the string 'ABRT', check for the exit
> code in both platforms. On msys (unit test environment), it is 9
> and on Linux, it is 134 (SIGABRT
There is no 'kill -l' type functionality available on Windows.
So instead of looking for the string 'ABRT', check for the exit
code in both platforms. On msys (unit test environment), it is 9
and on Linux, it is 134 (SIGABRT + 128).
On Windows, stderr is fully buffered if connected to a pipe.
Make
