public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ariel Burbaickij <ariel.burbaickij@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: David Allsopp <David.Allsopp@cl.cam.ac.uk>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Debugging malloc crash in gdb
Date: Wed, 19 Oct 2022 08:20:35 +0200	[thread overview]
Message-ID: <CANeJNHq1KMp71Be4=O5ofaGF_8Yu16L8N1WKzPb127jM-L33vw@mail.gmail.com> (raw)
In-Reply-To: <f4e9c183-a4b5-7c59-c608-9922beb76961@dronecode.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2113 bytes --]

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 <jon.turney@dronecode.org.uk>
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 moment, I know that we crash in malloc, so my main question is how
>> to
>> go further in gdb. I installed the cygwin-debuginfo package, but all I'm
>> getting is:
>>
>
> Firstly, if the crash is inside the cygwin DLL, you must follow the advice
> in [1], and use 'set cygwin-exceptions on' to tell gdb to stop on an
> exception inside cygwin itself.
>
> [1] https://cygwin.com/faq.html#faq.programming.debugging-cygwin
>
>
> /cygdrive/d/a/scallywag/gdb/gdb-11.2-1.x86_64/src/gdb-11.2/
>> gdb/infrun.c:2550
>> : internal-error: void resume_1(gdb_signal): Assertion
>> `pc_in_thread_step_range (pc, tp)' failed.
>>
>
> This looks similar to the gdb crash reported [2], which I just don't have
> any time to look into.
>
> [2] https://cygwin.com/pipermail/cygwin/2022-June/251714.html
>
> I'd suggest reporting this as directed in https://www.sourceware.org/gdb
> /bugs/
>
> (Note that self-service account creation is disabled on the sourceware
> bugzilla, due to spam problems, so you need to mail overseers as directed
> there, to request a Sourceware Bugzilla account.)
>
> The reproduction case is below (it's the OCaml runtime, so it's not exactly
>> minimal, but it seems to be very repeatable to get gdb to the position of
>> the crash).
>>
>> [...]
>
>>
>> Any assistance to debug this further hugely appreciated!
>>
>
> It might be worth exploring if this gdb crash is seen in older versions of
> gcc, or with older gcc...
>
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>

  reply	other threads:[~2022-10-19  6:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 10:35 David Allsopp
2022-10-18 19:08 ` Jon Turney
2022-10-19  6:20   ` Ariel Burbaickij [this message]
2022-11-02 12:38     ` Jon Turney
2022-11-02 13:24       ` Ariel Burbaickij
2022-10-20  8:22   ` David Allsopp
2022-10-20  9:38     ` Ariel Burbaickij
2022-11-02 12:38     ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANeJNHq1KMp71Be4=O5ofaGF_8Yu16L8N1WKzPb127jM-L33vw@mail.gmail.com' \
    --to=ariel.burbaickij@gmail.com \
    --cc=David.Allsopp@cl.cam.ac.uk \
    --cc=cygwin@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).