On 8/18/20 12:20 AM, Ken Brown via Cygwin wrote:
> On 8/17/2020 8:09 PM, JonY via Cygwin wrote:
>> On 8/17/20 8:50 PM, Ken Brown via Cygwin wrote:
This isn't an issue after all. The comment I quoted above refers to
all GCC exceptions, not just STATUS_GCC_THROW. I'll submit a patch
On 8/17/2020 8:09 PM, JonY via Cygwin wrote:
On 8/17/20 8:50 PM, Ken Brown via Cygwin wrote:
This isn't an issue after all. The comment I quoted above refers to
all GCC exceptions, not just STATUS_GCC_THROW. I'll submit a patch
after testing.
I've sent the patch. The output of the OP's tes
On 8/17/20 8:50 PM, Ken Brown via Cygwin wrote:
>>
>> This isn't an issue after all. The comment I quoted above refers to
>> all GCC exceptions, not just STATUS_GCC_THROW. I'll submit a patch
>> after testing.
>
> I've sent the patch. The output of the OP's test case is now the same
> on 64-bit
On 8/17/2020 4:40 PM, Ken Brown via Cygwin wrote:
On 8/17/2020 3:06 PM, Ken Brown via Cygwin wrote:
On 8/17/2020 2:13 PM, Corinna Vinschen wrote:
On Aug 17 13:36, Ken Brown via Cygwin wrote:
On 8/16/2020 6:38 PM, Ken Brown via Cygwin wrote:
One further comment, and then I'll shut up
I lied.
On 8/17/2020 3:06 PM, Ken Brown via Cygwin wrote:
On 8/17/2020 2:13 PM, Corinna Vinschen wrote:
On Aug 17 13:36, Ken Brown via Cygwin wrote:
On 8/16/2020 6:38 PM, Ken Brown via Cygwin wrote:
One further comment, and then I'll shut up
I lied.
...which is ok.
and leave it to people who kno
On 8/17/2020 2:13 PM, Corinna Vinschen wrote:
On Aug 17 13:36, Ken Brown via Cygwin wrote:
On 8/16/2020 6:38 PM, Ken Brown via Cygwin wrote:
One further comment, and then I'll shut up
I lied.
...which is ok.
and leave it to people who know what they're talking about: In the
64-bit case, t
Corinna Vinschen writes:
> This stuff isn't really my strong point. IIUC the above comment correctly,
> we might get away with adding another case to the exception handler switch:
>
> #define STATUS_GCC_THROW 0x20474343
> case STATUS_GCC_THROW:
> return ExceptionContinueExecution;
>
> Did
On Aug 17 13:36, Ken Brown via Cygwin wrote:
> On 8/16/2020 6:38 PM, Ken Brown via Cygwin wrote:
> > One further comment, and then I'll shut up
>
> I lied.
...which is ok.
> > and leave it to people who know what they're talking about: In the
> > 64-bit case, the function _Unwind_RaiseException
On 8/16/2020 6:38 PM, Ken Brown via Cygwin wrote:
On 8/16/2020 10:56 AM, Ken Brown via Cygwin wrote:
On 8/16/2020 9:52 AM, Takashi Yano via Cygwin wrote:
On Sun, 16 Aug 2020 09:21:24 -0400
Ken Brown via Cygwin wrote:
On 8/15/2020 11:53 PM, Takashi Yano via Cygwin wrote:
On Sat, 15 Aug 2020 2
On 8/16/2020 10:56 AM, Ken Brown via Cygwin wrote:
On 8/16/2020 9:52 AM, Takashi Yano via Cygwin wrote:
On Sun, 16 Aug 2020 09:21:24 -0400
Ken Brown via Cygwin wrote:
On 8/15/2020 11:53 PM, Takashi Yano via Cygwin wrote:
On Sat, 15 Aug 2020 20:38:01 -0300
David McFarland via Cygwin wrote:
On 8/16/2020 9:52 AM, Takashi Yano via Cygwin wrote:
On Sun, 16 Aug 2020 09:21:24 -0400
Ken Brown via Cygwin wrote:
On 8/15/2020 11:53 PM, Takashi Yano via Cygwin wrote:
On Sat, 15 Aug 2020 20:38:01 -0300
David McFarland via Cygwin wrote:
I was just debugging a c++ app (b2 build system from
Takashi Yano writes:
> On Sat, 15 Aug 2020 20:38:01 -0300
> David McFarland via Cygwin wrote:
>>
>> I was just debugging a c++ app (b2 build system from boost), and noticed
>> that it would appear to exit unexpectedly without an error. This turned
>> out to be when an unhandled C++ exception w
On Sun, 16 Aug 2020 09:21:24 -0400
Ken Brown via Cygwin wrote:
> On 8/15/2020 11:53 PM, Takashi Yano via Cygwin wrote:
> > On Sat, 15 Aug 2020 20:38:01 -0300
> > David McFarland via Cygwin wrote:
> >>
> >> I was just debugging a c++ app (b2 build system from boost), and noticed
> >> that it would
On 8/15/2020 11:53 PM, Takashi Yano via Cygwin wrote:
On Sat, 15 Aug 2020 20:38:01 -0300
David McFarland via Cygwin wrote:
I was just debugging a c++ app (b2 build system from boost), and noticed
that it would appear to exit unexpectedly without an error. This turned
out to be when an unhandl
On Sat, 15 Aug 2020 20:38:01 -0300
David McFarland via Cygwin wrote:
>
> I was just debugging a c++ app (b2 build system from boost), and noticed
> that it would appear to exit unexpectedly without an error. This turned
> out to be when an unhandled C++ exception was thrown.
>
> On a fresh inst
On 8/15/20 11:38 PM, David McFarland via Cygwin wrote:
>
> I was just debugging a c++ app (b2 build system from boost), and noticed
> that it would appear to exit unexpectedly without an error. This turned
> out to be when an unhandled C++ exception was thrown.
>
> On a fresh install of cygwin w
I was just debugging a c++ app (b2 build system from boost), and noticed
that it would appear to exit unexpectedly without an error. This turned
out to be when an unhandled C++ exception was thrown.
On a fresh install of cygwin with gcc-g++, this program will throw an
exception from the std::st
17 matches
Mail list logo
