public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: rih3306 <rob.hickey@us.bosch.com>
To: cygwin@cygwin.com
Subject: Re: building expect problems on W10
Date: Mon, 15 Jul 2019 13:42:00 -0000	[thread overview]
Message-ID: <1563198148321-0.post@n5.nabble.com> (raw)
In-Reply-To: <aa560db2-2a18-e16f-5f86-ee2dab743d45@SystematicSw.ab.ca>

Good suggestion thank you.

Can we please consider where I'm at presently before trying that?

I'm now able to build expect.exe and libexpect5.45.4.dll using this
configure line


./configure --disable-option-checking '--prefix=/usr/local' 
'--build=x86_64-unknown-cygwin' 'CC=/cygdrive/C/work/usr/local/bin/gcc'
'CFLAGS=-mcmodel=large' 'build_alias=x86_64-unknown-cygwin'
--cache-file=../config.cache --srcdir=. &>configure-out.txt


followed of course by make.

However,  running ./expect.exe produces a stackdump

which is here.

  Exception: STATUS_ACCESS_VIOLATION at rip=00000000000
rax=0000000000000000 rbx=0000000000800080 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=000000006D655AD3
r8 =0000000000000000 r9 =000000006CDEE551 r10=0000000000000000
r11=8101010101010100 r12=0000000000867580 r13=0000000000867590
r14=00000000008644F0 r15=0000000000867590
rbp=0000000000875EC0 rsp=00000000FFFFCA08
program=C:\work\___packages\expect\expect5.45.4\expect.exe, pid 940, thread
main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame        Function    Args
End of stack trace
 


I get the stackdump both with and without the memory model option in the
configure line.

Is it possible to tweak my configure line and get rid of the stackdump?

Thank you.



--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html

--
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:[~2019-07-15 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11 21:25 rih3306
2019-07-11 23:10 ` René Berber
2019-07-12 16:07   ` Brian Inglis
2019-07-15 13:42     ` rih3306 [this message]

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=1563198148321-0.post@n5.nabble.com \
    --to=rob.hickey@us.bosch.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).