public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Helmut Karlowski" <helmut.karlowski@ish.de>
To: cygwin@cygwin.com
Subject: texlive-install: core dumped
Date: Sat, 29 Jun 2013 11:43:00 -0000	[thread overview]
Message-ID: <op.wzfrolroofd6j1@nebbiolo.upc.de> (raw)

I've just updated my cygwin using setup.exe on XP-pro and found that the  
texlive-install produced an error.

In setup.log.full I found:

fmtutil: initial config file is `/etc/texmf/web2c/fmtutil.cnf'
fmtutil: configuration file updated: `/etc/texmf/web2c/fmtutil.cnf'
fmtutil: running `luatex -ini   -jobname=luatex -progname=luatex  
luatex.ini' ...
Memory fault (core dumped)
Error: `luatex -ini  -jobname=luatex -progname=luatex luatex.ini' failed

...

fmtutil: initial config file is `/etc/texmf/web2c/fmtutil.cnf'
fmtutil: configuration file updated: `/etc/texmf/web2c/fmtutil.cnf'
fmtutil: running `luatex -ini   -jobname=dviluatex -progname=dviluatex  
dviluatex.ini' ...
Memory fault (core dumped)
Error: `luatex -ini  -jobname=dviluatex -progname=dviluatex dviluatex.ini'  
failed

...

fmtutil: running `luatex -ini   -jobname=luatex -progname=luatex  
luatex.ini' ...
Memory fault (core dumped)
Error: `luatex -ini  -jobname=luatex -progname=luatex luatex.ini' failed

and more.

I don't know which process crashed (fmtutil is a shell-script), and I  
found no stackdump anywhere using

find . ( -path ./c -o -path ./cygdrive -o -path ./proc ) -prune -name  
'*.stackdump' -print

Are the stackdumps being deleted by setup? I could not reproduce a crash  
by running fmtutil --refresh manually.

With fmtutil --all I get at the end:

###############################################################################
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
   /home/adm/.cache/texmf/web2c
for details.
###############################################################################

This is a summary of all `failed' messages:
`pdftex -ini  -jobname=mllatex -progname=mllatex -translate-file=cp227.tcx  
-mltex mllatex.ini' failed
`xetex -ini  -jobname=xetex -progname=xetex -etex xetex.ini' failed
`xetex -ini  -jobname=xelatex -progname=xelatex -etex xelatex.ini' failed

But again no Memory fault.

How can I find out what caused the Memory fault?

CYGWIN_NT-5.1 1.7.20(0.266/5/3) 2013-06-07 11:11 i686

-- 
Helmut Karlowski

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2013-06-29 10:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29 11:43 Helmut Karlowski [this message]
2013-06-29 12:26 ` Ken Brown
2013-06-29 12:36   ` Helmut Karlowski
2013-06-29 15:20     ` Ken Brown
2013-06-29 18:37       ` Helmut Karlowski
2013-06-29 19:38         ` Ken Brown
2013-06-29 22:00           ` Helmut Karlowski
2013-06-29 23:37             ` Ken Brown
2013-06-30  2:34               ` Helmut Karlowski
2013-06-30  5:59                 ` Ken Brown
2013-06-30 14:36                   ` Helmut Karlowski
2013-06-30 15:36                     ` Ken Brown
2013-06-30 16:31                       ` Helmut Karlowski
2013-06-30 17:44                         ` Ken Brown
2014-04-04 10:59                           ` Václav Zeman
2014-04-04 13:14                             ` Ken Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.wzfrolroofd6j1@nebbiolo.upc.de \
    --to=helmut.karlowski@ish.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).