From: Patrick Herbst <paherbst@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Patch for run-1.3.0-1 core dump
Date: Mon, 09 Jun 2014 15:47:00 -0000 [thread overview]
Message-ID: <CACMdL5J5iCO46m6PakDwKnW3S-52QijRcKUQyo8MJ9U46UizpA@mail.gmail.com> (raw)
>>
>> On 3/20/2014 8:57 AM, Patrick Herbst wrote:
>>
>>> On 2/18/2014 4:16 AM, Corinna Vinschen wrote:
>>> Did my earlier patch get included? I haven't seen a "run" new version
>>> yet.
>>>
>>> http://www.cygwin.com/ml/cygwin/2013-12/msg00006.html
>>>
>>> My patch was the one that properly quote arguments. Maybe let's start
>>> with that before putting new stuff underneath it. From Chuck: "I'll
>>> roll a new update fairly soon."
>>
>>
>> http://www.cygwin.com/ml/cygwin/2013-12/msg00045.html
>>
>> I'm still looking for a released fix for this too. Thus far I've been
>> using run 1.2.
>>
>> Any word on this?
>
>
>
> In the mean time, you can run it from /usr/local/bin if you like:
>
> wget -O RUN-patch.txt 'http://pastebin.com/download.php?i=4SSPDGQh'
> export CVSROOT=:pserver:anoncvs@cygwin.com:/cvs/cygwin-apps
> cvs checkout run
> cd run
> patch -p0 < ../RUN-patch.txt
> autoreconf -vif
> ./configure --prefix=/usr/local
> make
> make install
>
> You end up with:
> /usr/local/bin/run.exe
> /usr/local/share/man/man1/run.1
Ok So run.exe has not been updated even though patches have been submitted.
Can this be released yet??
Current version 1.3 produces a stackdump every . single . time . it runs.
what is the test procedure for this application??
--
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 reply other threads:[~2014-06-09 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 15:47 Patrick Herbst [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-10 17:35 foo
2013-08-12 14:22 ` Charles Wilson
2014-02-18 3:53 ` Jon TURNEY
2014-02-18 6:13 ` Charles Wilson
2014-02-18 9:16 ` Corinna Vinschen
2014-02-18 9:35 ` Corinna Vinschen
2014-02-20 1:18 ` Max Polk
2014-03-20 15:03 ` Patrick Herbst
2014-03-21 4:49 ` Max Polk
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=CACMdL5J5iCO46m6PakDwKnW3S-52QijRcKUQyo8MJ9U46UizpA@mail.gmail.com \
--to=paherbst@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).