>Can you share a link to the gdb bug report?
https://sourceware.org/bugzilla/show_bug.cgi?id=29513
So, open source products' support reaction time is usually great but not
always great ;-). Unassigned for two months+ and counting.
Kind Regards
Ariel Burbaickij
On Wed, Nov 2, 2022 at 1:38 PM Jo
On 20/10/2022 09:22, David Allsopp wrote:
On Tue, 18 Oct 2022 at 20:09, Jon Turney wrote:
On 18/10/2022 11:35, David Allsopp wrote:
I'm wondering if I may be able to have some pointers for debugging what
seems to be an unexpected interaction between mmap/mprotect/munmap and
malloc with the OCam
On 19/10/2022 07:20, Ariel Burbaickij wrote:
Hello all,
I reported it already, of course as it happened to me but alas no reaction
so far.
Thanks for doing that.
Can you share a link to the gdb bug report?
--
Problem reports: https://cygwin.com/problems.html
FAQ: https
Hello David,
congrats on your bug fixing but gdb is pretty open that it considers it as
its own bug while running its "inferior", somewhere here:
if (tp->control.may_range_step)
{
/* If we're resuming a thread with the PC out of the step
range, then we're doing some nested/finer run control
operat
On Tue, 18 Oct 2022 at 20:09, Jon Turney wrote:
>
> On 18/10/2022 11:35, David Allsopp wrote:
> > I'm wondering if I may be able to have some pointers for debugging what
> > seems to be an unexpected interaction between mmap/mprotect/munmap and
> > malloc with the OCaml runtime.
> >
> > At the mome
Hello all,
I reported it already, of course as it happened to me but alas no reaction
so far.
Kind Regards
Ariel Burbaickij
On Tuesday, October 18, 2022, Jon Turney
wrote:
> On 18/10/2022 11:35, David Allsopp wrote:
>
>> I'm wondering if I may be able to have some pointers for debugging what
>>
On 18/10/2022 11:35, David Allsopp wrote:
I'm wondering if I may be able to have some pointers for debugging what
seems to be an unexpected interaction between mmap/mprotect/munmap and
malloc with the OCaml runtime.
At the moment, I know that we crash in malloc, so my main question is how to
go
I'm wondering if I may be able to have some pointers for debugging what
seems to be an unexpected interaction between mmap/mprotect/munmap and
malloc with the OCaml runtime.
At the moment, I know that we crash in malloc, so my main question is how to
go further in gdb. I installed the cygwin-debug
8 matches
Mail list logo
