From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: clisp crashes on startup
Date: Sat, 07 Jul 2012 13:04:00 -0000 [thread overview]
Message-ID: <4FF833DC.8090908@gmail.com> (raw)
In-Reply-To: <4FF76A98.2020309@dancol.org>
On 7/7/2012 12:45 AM, Daniel Colascione wrote:
> $ clisp
Trimming a bit ?
>
> Welcome to GNU CLISP 2.48 (2009-07-28) <http://clisp.cons.org/>
>
>
> Type :h and hit Enter for context help.
>
> Segmentation fault (core dumped)
no issue on W7/64
>
> $ cat lisp.exe.stackdump
> Exception: STATUS_ACCESS_VIOLATION at eip=00421614
> eax=80020000 ebx=002965B3 ecx=805034FD edx=002965B0 esi=801DB65D
> edi=005C651C
> ebp=01335B18 esp=01335B10 program=C:\lib\clisp-2.48\base\lisp.exe, pid
> 4092, thread main
> cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
> Stack trace:
> Frame Function Args
> 01335B18 00421614 (01335D5C, 01335D68, 00000000, 00000001)
> 01335D78 0042C0C1 (004FE2A2, 10020028, 01336148, 004C1F7D)
> 01335D88 0042DAEC (00487E4C, 00020002, 00000000, 00020000)
> 01336148 004C1F7D (0042DAD8, 8023650D, 01336198, 0046527B)
> 01336198 00425E7A (80056A34, 00000007, 80229E5D, 002B002B)
> 01336268 00426D9B (00000015, 8005A0F0, 013363D8, 610256D9)
> 013362A8 004767FA (00000002, 642F7372, 6F636E61, 002E2F6C)
> 013363D8 00491599 (802346D9, 802C679B, 00503501, 00000001)
> 013364E8 0049589B (00507981, 00000001, 801FB682, 0047E704)
> 01336588 004823A8 (800568E0, 01336764, 800D11B2, 0047E704)
> 01336628 004846B3 (800CF45D, 00000003, 800D1076, 0047E704)
> 013366C8 0048277A (000001E8, 00000004, 01336744, 80051BF4)
> 01336768 004846B3 (800D1045, 00000003, 80051C44, 80051C90)
> 013368E8 0048277A (FFDA0074, 004FEFE0, 00000001, 0133696C)
> 01336988 004846B3 (00504F41, 00000003, 005C66D0, 005034E1)
> 01336BD8 0042F32B (6127B418, 80229E5D, 00004000, 005034E1)
> End of stack trace (more stack frames may be present)
>
your mount table looks strange
C: / system binary,auto
c:\bin /bin system text,cygexec
c:/bin /usr/bin system text,cygexec
C:\lib /usr/lib system binary,auto
c:\usr\local\bin /usr/local/bin system text,cygexec
cygdrive prefix /drv system binary,auto
It is not recommended to use c:\ as root.
Why half are mounted as text instead of binary ?
Regards
Marco
--
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:[~2012-07-07 13:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 22:47 Daniel Colascione
2012-07-07 13:04 ` marco atzeri [this message]
2012-07-07 13:41 ` Daniel Colascione
2012-07-07 16:19 ` Reini Urban
2012-07-07 17:45 ` marco atzeri
2012-07-07 19:08 ` Daniel Colascione
2012-07-09 21:01 ` Reini Urban
2012-07-09 21:27 ` Daniel Colascione
2012-07-10 4:59 ` Daniel Colascione
2012-07-10 8:14 ` Corinna Vinschen
2012-07-10 15:42 ` Daniel Colascione
2012-07-13 3:48 ` Daniel Colascione
2012-07-13 7:41 ` Corinna Vinschen
2012-07-13 12:53 ` Reini Urban
2012-07-13 14:27 ` Corinna Vinschen
2012-07-13 16:30 ` Reini Urban
2012-07-13 17:46 ` Daniel Colascione
2012-07-07 17:05 ` Andrey Repin
2012-07-07 19:04 ` Daniel Colascione
2012-07-08 23:20 ` Andrey Repin
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=4FF833DC.8090908@gmail.com \
--to=marco.atzeri@gmail.com \
--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).