On 2017-07-07 15:43, Ken Brown wrote:
On 7/7/2017 11:12 AM, Ken Brown wrote:
On 7/6/2017 8:26 AM, Masamichi Hosoda wrote:
On Cygwin 2.8.1 x86_64, I've found that g++ std:map initializing
may raise segmentation fault.
The binary compiled with cygwin-devel-2.8.0-1
does not raise segmentation faul
On 7/7/2017 11:12 AM, Ken Brown wrote:
On 7/6/2017 8:26 AM, Masamichi Hosoda wrote:
Hello,
On Cygwin 2.8.1 x86_64, I've found that g++ std:map initializing
may raise segmentation fault.
The binary compiled with cygwin-devel-2.8.0-1
does not raise segmentation fault
even if on Cygwin 2.8.1 x86_6
NEWS:
=
See CHANGES (URL below) for more information about the differences
between 1.8.0 and previous Subversion releases.
IMPORTANT: Please read the release notes (URL below) before
upgrading from a previous major release. 1.8 includes a new working
copy format with a manual upgrade operation
Dear maintainer of git
I use CrashPlan as my backup engine. It has difficulty backing up
files with no "other" access. Many git locale (.mo) and doc-related
files have permissions 600 (directories 700). Is there a good reason
for this? I would think that 644 and 755 access would be fine
> On 07/07/2017 16:21, Ivan Gagis wrote:
>> I installed g++ 6.3.0-2 and still can reproduce the segfault :(.
>>
>> Br,
>> Ivan
>>
>
> It seems due to the -std=c++11 restriction
>
> $ g++ foo.cc
>
> $ ./a.exe
> Hello World!
>
> $ g++ -std=c++11 foo.cc
>
> $ ./a.exe
> Segmentation fault (core du
On 7/6/2017 8:26 AM, Masamichi Hosoda wrote:
Hello,
On Cygwin 2.8.1 x86_64, I've found that g++ std:map initializing
may raise segmentation fault.
The binary compiled with cygwin-devel-2.8.0-1
does not raise segmentation fault
even if on Cygwin 2.8.1 x86_64 environments.
So I suspect cygwin-dev
On Mon, Jul 03, 2017 at 03:31:22PM +0200, Corinna Vinschen wrote:
> I uploaded a new Cygwin release 2.8.1-1
This has introduced a regression that I'm seeing when running `ls` on
some network shares. I can reproduce the behaviour with an install of
only the base Cygwin packages, and the behaviour
On 07/07/2017 16:21, Ivan Gagis wrote:
I installed g++ 6.3.0-2 and still can reproduce the segfault :(.
Br,
Ivan
It seems due to the -std=c++11 restriction
$ g++ foo.cc
$ ./a.exe
Hello World!
$ g++ -std=c++11 foo.cc
$ ./a.exe
Segmentation fault (core dumped)
--
Problem reports: ht
I installed g++ 6.3.0-2 and still can reproduce the segfault :(.
Br,
Ivan
2017-07-07 17:09 GMT+03:00 Masamichi Hosoda :
>> On 07/07/2017 14:51, Marco Atzeri wrote:
>>> On 06/07/2017 14:26, Masamichi Hosoda wrote:
Hello,
On Cygwin 2.8.1 x86_64, I've found that g++ std:map initializi
> On 07/07/2017 14:51, Marco Atzeri wrote:
>> On 06/07/2017 14:26, Masamichi Hosoda wrote:
>>> Hello,
>>>
>>> On Cygwin 2.8.1 x86_64, I've found that g++ std:map initializing
>>> may raise segmentation fault.
>>> The binary compiled with cygwin-devel-2.8.0-1
>>> does not raise segmentation fault
>>
On 2017-07-07 00:49, Michael Jun wrote:
> On Friday, July 07, 2017 12:30 PM, Michael Jun wrote:
> When I invoke system terminal programs from gnome/openbox desktop menu,
> most of them including gnome-terminal produce the following message.
> Warning: no access to tty (Inappropriate ioctl for devi
On 07/07/2017 14:51, Marco Atzeri wrote:
On 06/07/2017 14:26, Masamichi Hosoda wrote:
Hello,
On Cygwin 2.8.1 x86_64, I've found that g++ std:map initializing
may raise segmentation fault.
The binary compiled with cygwin-devel-2.8.0-1
does not raise segmentation fault
even if on Cygwin 2.8.1 x86
On 06/07/2017 14:26, Masamichi Hosoda wrote:
Hello,
On Cygwin 2.8.1 x86_64, I've found that g++ std:map initializing
may raise segmentation fault.
The binary compiled with cygwin-devel-2.8.0-1
does not raise segmentation fault
even if on Cygwin 2.8.1 x86_64 environments.
So I suspect cygwin-dev
Hi,
I'm having the same problem after updating to latest cygwin packages.
It seems quite important problem, are there any plans to fix it?
Trying to debug the test program from Masamichi Hosoda it can be seen
that crash occurs in std::map implementation, see stacktrace below. I
wonder if there wa
> Bonus points if you can reduce this testcase further, see
> https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction
> for how to take the preprocessed output and automatically
> reduce it to a much smaller file.
I attach the output of
```
creduce checki.sh test_getline.i
```
where checki.s
15 matches
Mail list logo