Hi Ken,
> I think you're probably right. The use of FE_NNF in execvp* was
> introduced in
> commit 6d63272b. I suspect it was just an oversight that the spawvp*
> functions
> weren't changed in the same way. I'll send a patch to the cygwin-
> patches list
> to fix this. When Corinna returns
On 2019-10-09 11:10, Jon Turney wrote:
> On 09/10/2019 16:31, Brian Inglis wrote:
>> On 2019-10-09 01:14, Biswapriyo Nath wrote:
>>> * mintty version: mintty 3.0.6 (x86_64-pc-cygwin) * cygwin version:
>>> 3.1.0-0.6 * code:
>>>
>>> #include
>>>
>>> int main() { int x = 1; assert(x == 0); }
>>>
>
On 10/9/2019 4:03 PM, Stephen Carrier wrote:
> On Wed, Oct 02, 2019 at 01:38:13PM -0600, Brian Inglis wrote:
>> On 2019-10-02 12:18, Stephen Carrier wrote:
>>> On Tue, Oct 01, 2019 at 08:43:40PM -0600, Brian Inglis wrote:
On 2019-10-01 18:47, Stephen Carrier wrote:
> The latest verion of t
On Wed, Oct 02, 2019 at 01:38:13PM -0600, Brian Inglis wrote:
> On 2019-10-02 12:18, Stephen Carrier wrote:
> > On Tue, Oct 01, 2019 at 08:43:40PM -0600, Brian Inglis wrote:
> >> On 2019-10-01 18:47, Stephen Carrier wrote:
> >>> The latest verion of the msmtp package: 1.8.5+20190811+git7912c76-1 .
On 09/10/2019 16:31, Brian Inglis wrote:
On 2019-10-09 01:14, Biswapriyo Nath wrote:
* mintty version: mintty 3.0.6 (x86_64-pc-cygwin)
* cygwin version: 3.1.0-0.6
* code:
#include
int main() {
int x = 1;
assert(x == 0);
}
* Expected result: The terminal should show this message which a
On 10/7/2019 4:51 PM, donpedro.tdcadsl.dk via cygwin wrote:
> Hi all,
>
> While working on something i noticed that execvp* and spawnvp* behave
> differently with regards to $PATH, which i think is not correct.
>
> --
>
> 1) The execvp* functions are
On 2019-10-09 01:14, Biswapriyo Nath wrote:
> * mintty version: mintty 3.0.6 (x86_64-pc-cygwin)
> * cygwin version: 3.1.0-0.6
> * code:
>
> #include
>
> int main() {
> int x = 1;
> assert(x == 0);
> }
>
> * Expected result: The terminal should show this message which appers
> in latest stab
>From Takashi Yano's query, I ran those command, the last one shows the
assertion output. But wait! I rename the home folder (~) in cygwin
then revert it back. Now there is no issue. Don't know what happened.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://c
> Is this surely the reply to "Re: assert does not show output in
> cygwin test build" ?
>
> Or your reply is regarding "Cygwin and stdexcept bug ?" ?
Ops, sorry, messed up. :)
The latter of course.
Kind regards,
Pavel Fedin
Senior Engineer
Samsung Electronics Research center Russia
--
Prob
On Wed, 9 Oct 2019 13:39:42 +0300
"Pavel Fedin" wrote:
> Hello!
>
> > Thanks for your report. However, I cannot reproduce the problem.
> >
> > 1. Could you please describe the steps to reproduce this?
>
> g++ test.cpp -o test
> ./test
>
> > 2. What happens if you execute:
> > ./a.exe 2>&1 | c
Hello!
> Thanks for your report. However, I cannot reproduce the problem.
>
> 1. Could you please describe the steps to reproduce this?
g++ test.cpp -o test
./test
> 2. What happens if you execute:
> ./a.exe 2>&1 | cat
The same. No output.
From gdb i know that the control reaches __cxa_thr
On Wed, 9 Oct 2019 12:44:14 +0530
Biswapriyo Nath wrote:
> * mintty version: mintty 3.0.6 (x86_64-pc-cygwin)
> * cygwin version: 3.1.0-0.6
> * code:
>
> #include
>
> int main() {
> int x = 1;
> assert(x == 0);
> }
>
> * Expected result: The terminal should show this message which appers
> i
Hello everyone!
On Linux if a C++ application throws uncaught error, there's explanation given:
--- cut ---
terminate called after throwing an instance of 'std::runtime_error'
what(): Just throw up
Aborted
--- cut ---
On 64-bit Cygwin the same code simply silently aborts, giving no hints. I
* mintty version: mintty 3.0.6 (x86_64-pc-cygwin)
* cygwin version: 3.1.0-0.6
* code:
#include
int main() {
int x = 1;
assert(x == 0);
}
* Expected result: The terminal should show this message which appers
in latest stable cygwin version.
assertion "x == 0" failed: file "test.c", line 6, f
14 matches
Mail list logo
