On Thu, Feb 6, 2025 at 2:57 PM Qing Zhao wrote:
>
>
>
> > On Feb 6, 2025, at 04:36, Richard Biener wrote:
> >
> > On Wed, Feb 5, 2025 at 4:40 PM Qing Zhao wrote:
> >>
> >>
> >>
> >>> On Feb 5, 2025, at 07:46, Richard Biener
> >>> wrote:
> >>>
> >>> On Tue, Feb 4, 2025 at 10:12 PM Qing Zhao wr
> On Feb 6, 2025, at 09:25, Richard Biener wrote:
>
> On Thu, Feb 6, 2025 at 2:57 PM Qing Zhao wrote:
>>
>>
>>
>>> On Feb 6, 2025, at 04:36, Richard Biener wrote:
>>>
>>> On Wed, Feb 5, 2025 at 4:40 PM Qing Zhao wrote:
> On Feb 5, 2025, at 07:46, Richard Biener
>>
> On Feb 6, 2025, at 04:36, Richard Biener wrote:
>
> On Wed, Feb 5, 2025 at 4:40 PM Qing Zhao wrote:
>>
>>
>>
>>> On Feb 5, 2025, at 07:46, Richard Biener wrote:
>>>
>>> On Tue, Feb 4, 2025 at 10:12 PM Qing Zhao wrote:
Hi,
One of our big application segv in libgcc
On Wed, Feb 5, 2025 at 4:40 PM Qing Zhao wrote:
>
>
>
> > On Feb 5, 2025, at 07:46, Richard Biener wrote:
> >
> > On Tue, Feb 4, 2025 at 10:12 PM Qing Zhao wrote:
> >>
> >> Hi,
> >>
> >> One of our big application segv in libgcc code while unwinding the stack.
> >>
> >> This is a random crash wh
> On Feb 5, 2025, at 07:49, Jakub Jelinek wrote:
>
> On Wed, Feb 05, 2025 at 01:46:02PM +0100, Richard Biener wrote:
>>> Please let me know any comments on this?
>>
>> I think I've seen this elsewhere -- the issue is the unwind register API does
>> not allow for failures but I also think calli
> On Feb 5, 2025, at 07:46, Richard Biener wrote:
>
> On Tue, Feb 4, 2025 at 10:12 PM Qing Zhao wrote:
>>
>> Hi,
>>
>> One of our big application segv in libgcc code while unwinding the stack.
>>
>> This is a random crash while the application throws a c++ exception and
>> unwinds the stack
On Wed, Feb 05, 2025 at 01:46:02PM +0100, Richard Biener wrote:
> > Please let me know any comments on this?
>
> I think I've seen this elsewhere -- the issue is the unwind register API does
> not allow for failures but I also think calling abort() is bad.
>
> Are you calling this from a JIT cont
On Tue, Feb 4, 2025 at 10:12 PM Qing Zhao wrote:
>
> Hi,
>
> One of our big application segv in libgcc code while unwinding the stack.
>
> This is a random crash while the application throws a c++ exception and
> unwinds the stack. Incidents are random and never can be reproduced by any
> test cas