[Octave-bug-tracker] [bug #60742] test failure in hgsave.m with Octave 6.2.90 (on Windows)

[Rik]

Follow-up Comment #4, bug #60742 (project octave):

Which BIST test is failing?  Is it the one identified by Markus in comment
#1?

For debugging, the first thing to do is locate the failing test and then
extract it from hgsave.m.  It might be that previous tests have somehow
corrupted the state of the graphics system and you want to be able to run the
test on its own.  Assuming you have put the BIST test in tst_hgsave.m, then
run 'test tst_hgsave' in a new version of Octave that you have run with the
'-f' switch so you are not reading any user or system initialization files.

If that still fails, then change the code from a BIST to an ordinary script by
removing the leading '%!' characters.  Run 'tst_hgsave' in a newly started
version of Octave with the '-f' switch.

If that still fails, change "visible", "off" option to "visible", "on".  Run
'tst_hgsave' in a newly started Octave version.

If that still fails, prime the debugger by typing 'dbstop tst_hgsave'.  Then
type 'tst_hgsave' to have the debugger stop in the first line.  Now use
'dbstep' to go line-by-line through the code.  See if the two figures created
look like each other.  Maybe there is an obvious difference such as a menubar
missing.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60742>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/