[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using debug_on_warning
From: |
fgnievinski |
Subject: |
Re: Using debug_on_warning |
Date: |
Wed, 26 Feb 2014 06:34:06 -0800 (PST) |
On Wed, Feb 26, 2014 at 4:11 AM, Thomas Weber-3 [via Octave] <
address@hidden> wrote:
> On Tue, Feb 25, 2014 at 05:09:32PM +0100, Markus Appel wrote:
> > This warning can be caused e.g. by printf("%s",5) when the argument is
> > converted implicitly to string type. When I put only that command in a
> > script file and execute it with debug_on_warning enabled, octave 3.8.0
> > drops as expected into debug mode. You can send your function file for
> > more information.
>
> I found the issue by going through the code.
> Essentially, it is the following:
>
> str = [];
> sprintf("%s", str);
>
> Now, with respect to 'my' code - this is not really my code. I am looking
> at matlab2tikz and the code in question is executed as part of the acid
> test shipped with it. The file is publically available at
> https://raw.github.com/nschloe/matlab2tikz/master/src/matlab2tikz.m
>
> The issue happens in the function drawPatch().
>
> warning: implicit conversion from null_matrix to sq_string
does trigger debug_on_warning for me, with Octave 3.8 --
it still doesn't for you? what Octave version?
-F.
--
View this message in context:
http://octave.1599824.n4.nabble.com/Using-debug-on-warning-tp4662035p4662353.html
Sent from the Octave - General mailing list archive at Nabble.com.