[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] write doc failure

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] write doc failure
Date: Tue, 5 Jul 2011 21:43:43 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

> Error printing document (generic_document). Consult gory log for details.

Let's look at the log:

> > 2011-07-04 16:08:18  ERROR 
> > (c:\workplace\gnumed-client.0.9.6\build\pyi.win32\setup\outpyz1.pyz\gnumed.pycommon.gmshellapi::run_command_in_shell()
> >  #139): platform does not support exit status differentiation

This log line only happens after a print command has been run.

On Windows this is very likely a gm-print_doc.bat in the PATH.

Since the log is without --debug we do not know the exit
code of gm-print_doc.bat which would be logged if GNUmed was
run with --debug.

In GNUmed 0.9 the print command is called without
explicitely setting acceptable exit codes. Thus, only exit
code 0 is acceptable (as is customary for success). This
tells us that gm-print_doc.bat did not return with the exit
code 0.

1) we need a GNUmed log with --debug to know what gm-print_doc.bat
   *actually* returns

2) I need the exact gm-print_doc.bat to be able to reason
   more about what to expect

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]