[petsc-users] Issues with log_view on windows

[Satish Balay]

Ah yes..

PATH=C:\cygwin64\usr\local\bin;C:\cygwin64\bin;C:\cygwin64\bin;C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2020.2.254\windows\mpi\intel64\bin;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\mpirt;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\mpirt;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\compiler;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\compiler;C:\Program Files\Microsoft MPI\Bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps;C:\cygwin64\lib\lapack

Satish


On Mon, 22 Nov 2021, Matthew Knepley wrote:

> On Mon, Nov 22, 2021 at 11:57 AM Barry Smith <bsmith at petsc.dev> wrote:
> 
> >
> >   What does Windows use for a path separator?
> >
> 
> semicolon
> 
> Maybe we could use either one as a separator, since semicolon is also used
> by the UNIX shell.
> 
>    Matt
> 
> 
> > On Nov 22, 2021, at 11:19 AM, Satish Balay via petsc-users <
> > petsc-users at mcs.anl.gov> wrote:
> >
> > Well our build tools use cygwin - but the library is built with MS/Intel
> > compilers - they use paths in windows notation.
> >
> > I'm not sure if there is a way to get windows PATHs without ':'
> >
> > Satish
> >
> > On Mon, 22 Nov 2021, Matthew Knepley wrote:
> >
> > On Mon, Nov 22, 2021 at 10:36 AM Milan Pelletier <
> > milan.pelletier at protonmail.com> wrote:
> >
> > Matt,
> > Thanks for the answer. I could fix my issue regarding unbalanced events -
> > and so SNES ex5 does work well too.
> > By the way, such imbalance does not trigger errors when log_view is using
> > plain ascii output, but it does fail when ascii_xml is used instead.
> >
> >
> > Yes, we have a "failsafe" for the regular logging, but the XML is
> > specifically hierarchical and we do not know how to close it. We could take
> > another look at that.
> >
> >
> > Unfortunately, regarding absolute paths, I had also tried to use cygwin
> > paths (`/cygdrive/c/...`) but that does not work either.
> >
> >
> > Hmm, that should work I think. Satish, do we have a machine to login and
> > test something like this?
> >
> >  Thanks,
> >
> >     Matt
> >
> >
> > Best,
> > Milan
> >
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > Le lundi 22 novembre 2021 à 2:39 PM, Matthew Knepley <knepley at gmail.com>
> > a écrit :
> >
> > On Mon, Nov 22, 2021 at 5:38 AM Milan Pelletier via petsc-users <
> > petsc-users at mcs.anl.gov> wrote:
> >
> > Dear PETSc team,
> >
> > The way some options are passed to PETSc can be an issue on Windows, in
> > particular regarding the "log_view" option.
> > Since the colon ':' character is used as a separator, I do not see how
> > absolute paths should be provided on Windows (since the drive name includes
> > a colon). Is there a trick / workaround to overcome this?
> >
> >
> > I thought we used Cygwin paths, but maybe one of the Windows people knows
> > better.
> >
> >
> > Besides, when I try to use the ascii_xml format, it crashes in file
> > xmllogevent.c, on line 751:
> >  illegalEvent = 1+nestedEvents[nNestedEvents-1].nstEvent;
> > (since nestedEvents is NULL).
> >
> >
> > This likely means that you have unbalanced events. I can run this on
> > examples. For instance does SNES ex5 work for you?
> >
> >  Thanks,
> >
> >     Matt
> >
> >
> > I'm using PETSc version 3.16.1 (using `git checkout tags/v3.16.1`).
> >
> > Thanks for your help,
> > Best regards,
> > Milan Pelletier
> >
> >
> >
> > --
> > What most experimenters take for granted before they begin their
> > experiments is infinitely more interesting than any results to which their
> > experiments lead.
> > -- Norbert Wiener
> >
> > https://www.cse.buffalo.edu/~knepley/
> > <http://www.cse.buffalo.edu/~knepley/>
> >
> >
> >
> 
>