From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: texlive-install: core dumped
Date: Sun, 30 Jun 2013 05:59:00 -0000 [thread overview]
Message-ID: <51CF9918.5020602@cornell.edu> (raw)
In-Reply-To: <op.wzgxhts2ofd6j1@nebbiolo.upc.de>
On 6/29/2013 9:38 PM, Helmut Karlowski wrote:
> Ken Brown, 30.06.2013 00:46:28:
>
>> No. setup.ini lists the packages that are available for install.
>> Often there is a "previous" version as well as a "current" version. This
>
> Ok - my guess was wrong then, thanks. xetex and luatex where not installed.
>
>>> 1. pdfetex -progname latex $*
>>>
>>> 2. dvipdfm -p a4 $*
>>
>> I just tried these commands with no problems:
>
> Maybe I'm using an outdated sty-file (e.g. dinbrief.sty), will look at
> it later. Is there a database of all styles, fonts etc. for all
> texlive-packages?
Does http://cygwin.com/packages/ give you what you're looking for? Or
maybe you want texlive.tlpdb, available at
http://www.ctan.org/tex-archive/systems/texlive/tlnet/tlpkg
> I re-installed luatex and found a stackdump-file (under /tmp during the
> setup-run):
>
> Exception: STATUS_ACCESS_VIOLATION at eip=0045F3B6
> eax=20018788 ebx=20020000 ecx=00000000 edx=00000002 esi=20011930
> edi=20018788
> ebp=0022AB68 esp=0022AB30 program=C:\cygwin\bin\luatex.exe, pid 3708,
> thread main
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> Stack trace:
> Frame Function Args
> 0022AB68 0045F3B6 (20011930, 00000000, 00000000, 00000001)
> 0022AB98 0040420D (0065B104, 006B7A82, 006B7351, 0065B140)
> 0022AC68 004029D6 (00000005, 0022ACB0, 0022ACB8, 0022ACB0)
> 0022AC88 00401790 (00000005, 0022ACB0, 20010100, 611A3F1B)
> 0022AD28 61008221 (00000000, 0022CDA8, 61007710, 00000000)
> End of stack trace
>
> According to setup.log.full all 4 luatex-calls crash. I have to mention
> I'm not using a shell available by cygwin, but something I'm working on,
> that's why I want to know why it crashes.
If you want to try debugging this with gdb, the texlive-debuginfo
package contains the files you need.
Ken
--
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
next prev parent reply other threads:[~2013-06-30 2:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 11:43 Helmut Karlowski
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 [this message]
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=51CF9918.5020602@cornell.edu \
--to=kbrown@cornell.edu \
--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).