You could shadow the buil-in warning function and grab the stacktrace manually
msgBack = lastwarn;
warnBack = warning;
traceBack = warning('query', 'backtrace');
warning('on', 'backtrace');
warning('on');
BackTrace = evalc('warning(''Error appeared in:'')');
BackTrace(strfind(BackTrace, char(8))) = [];
BackTrace(strfind(BackTrace, '{')) = [];
BackTrace(strfind(BackTrace, '}')) = [];
if strncmpi(BackTrace, 'warning: ', 9) % Remove initial 'Warning: '
BackTrace(1:9) = [];
end
BackTrace = strsplit(BackTrace, '\n');
BackTrace(strncmp(BackTrace, '> ', 2)) = []; % 1st line: '> SuError...'
if length(BackTrace) == 1
BackTrace{2} = ' Command line';
end
% Restore original state of WARNING:
if ~isempty(traceBack)
warning(traceBack);
end
warning(warnBack);
lastwarn(msgBack);
Now you have to replace all calls of builtin('warning') by builtin('warning') and care for the outputs.
But this is such ugly and it would be horrible, if a programming error conceals important warnings. Therefore I would never use this for serious code. (I use this code snippet to get a stack-trace in a user-defined Error class only.)
Think about using another method than the stacktrace to track the warning. What about parsing the output to the command window? See FEX: CmdWinTool for a method to get the text from it.
