Ehy Kurtis, Ehy TheDiveO thanks for the answer.
Yes English is not my native language and I try to be precise as best as I
can with my capabilities, thanks a lot for the patience and the effort on
your side to understand what I'm sayings. Now that I read your answer is a
little bit clearer how t
CMAC_resume might be something from here, IIRC Darwin's OpenBSD
anchestry: https://man.openbsd.org/CMAC_Init.3
On Monday, September 11, 2023 at 8:17:44 AM UTC+2 Kurtis Rader wrote:
> On Sun, Sep 10, 2023 at 10:41 PM Danilo bestbug
> wrote:
>
>> Hey Robert,
>> The problem is not reproducible in
On Sun, Sep 10, 2023 at 10:41 PM Danilo bestbug <
bestbug.corporat...@gmail.com> wrote:
> Hey Robert,
> The problem is not reproducible in our test env but it occours on final
> user. To make thing thougher is not even an application we develop directly
> but is from one of our reseller, so we don
Hey Robert,
The problem is not reproducible in our test env but it occours on final
user. To make thing thougher is not even an application we develop directly
but is from one of our reseller, so we don't have direct access to the rest
of the codebase. Again I want to stress the main point of my
This most likely means your other code is corrupting the go runtime/heap/stack.
I would run other tests on this code exclusively (asan, etc).
> On Sep 10, 2023, at 12:54 PM, Danilo bestbug
> wrote:
>
>
> Hey TheDiveO, thanks for answering.
> My focus is not to hide the signal but I would
Hey TheDiveO, thanks for answering.
My focus is not to hide the signal but I would like to understand if this
behavior is wanted and in that case what we can do to avoid to have crash
report where the crashed thread does not run any of our "code".
Il giorno domenica 10 settembre 2023 alle 18:1
Maybe this SO Q with A might also help with further details:
https://stackoverflow.com/questions/47869988/how-does-cgo-handle-signals
On Friday, September 8, 2023 at 11:38:38 PM UTC+2 Danilo bestbug wrote:
> Ehy Ian, thanks for the response. Apology if I was not clear, I try to
> explain in a d
You seem to be barking up the wrong tree, at least for the moment. Maybe
your team may want to learn more about cgo and by sheer coincidence there's
a blog post https://shane.ai/posts/cgo-performance-in-go1.21/ that might
serve as a starting point, with one or two pointers to go further. I als
Ehy Ian, thanks for the response. Apology if I was not clear, I try to
explain in a different way but it's hard for me too since I'm not 100%
confident about what it's happening here exactly, I'm tring to follow the
trace but any feedback is more than welcome.
The problem I'm facing is the follo
On Thu, Sep 7, 2023 at 11:41 PM Danilo bestbug
wrote:
>
> Some weeks ago I've opened a possible bug on github and the only response I
> received is a reference to
> "This looks like the program (the Go runtime, or not) intentionally crashing
> when it is already in a bad condition, like receivin
10 matches
Mail list logo
