[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Segmentation Fault with Octave MXE under Windows
From: |
ijourneaux |
Subject: |
Re: Segmentation Fault with Octave MXE under Windows |
Date: |
Wed, 9 Jul 2014 14:34:40 -0700 (PDT) |
Daniel Sebald wrote
> virtual ~Array (void)
> {
> if (!rep)
> {
> fprintf(stderr, "NULL POINTER! RETURNING.\n");
> return;
> }
>
> if (--rep->count == 0)
> {
> delete rep;
> rep = NULL;
> }
> }
Under these circumstances, where the octave window is closed, where does
stderr get output to?
--
View this message in context:
http://octave.1599824.n4.nabble.com/Segmentation-Fault-with-Octave-MXE-under-Windows-tp4664305p4665362.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.
- Re: Segmentation Fault with Octave MXE under Windows, ijourneaux, 2014/07/05
- Re: Segmentation Fault with Octave MXE under Windows, ijourneaux, 2014/07/09
- Re: Segmentation Fault with Octave MXE under Windows, Daniel J Sebald, 2014/07/09
- Re: Segmentation Fault with Octave MXE under Windows,
ijourneaux <=
- Re: Segmentation Fault with Octave MXE under Windows, Daniel J Sebald, 2014/07/09
- Re: Segmentation Fault with Octave MXE under Windows, ijourneaux, 2014/07/09
- Re: Segmentation Fault with Octave MXE under Windows, ijourneaux, 2014/07/10
- Re: Segmentation Fault with Octave MXE under Windows, ijourneaux, 2014/07/10
- Re: Segmentation Fault with Octave MXE under Windows, Carnë Draug, 2014/07/10
- Message not available
- Re: Segmentation Fault with Octave MXE under Windows, Carnë Draug, 2014/07/10
- Re: Segmentation Fault with Octave MXE under Windows, Daniel J Sebald, 2014/07/10
- Re: Segmentation Fault with Octave MXE under Windows, Carnë Draug, 2014/07/10
- Re: Segmentation Fault with Octave MXE under Windows, ijourneaux, 2014/07/10
- Re: Segmentation Fault with Octave MXE under Windows, Daniel J Sebald, 2014/07/10