public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH] fhandler_pipe: add sanity limit to handle loops
Date: Thu, 30 Dec 2021 15:44:00 +0000	[thread overview]
Message-ID: <9796eaa8-07f1-0f14-3105-9ce482005b17@dronecode.org.uk> (raw)
In-Reply-To: <alpine.BSO.2.21.2112282143180.11760@resin.csoft.net>

On 29/12/2021 05:45, Jeremy Drake wrote:
> On Mon, 27 Dec 2021, Jon Turney wrote:
> 
>> On 24/12/2021 00:29, Jeremy Drake via Cygwin-patches wrote:
>>> again, so I can't confirm this.  I took a core with 'dumper' but gdb
>>> doesn't want to load it (it says Core file format not supported, maybe
>>> something with msys2's gdb?).
>>
>> I think you need gdb 11 (for this patch set [1], which is also in cygwin's
>> gdb 10 package) to read x86_64 cygwin core dumps.
>>
>> [1] https://sourceware.org/pipermail/gdb-patches/2020-August/171232.html
> 
> Thanks, this was the problem.  But the core dump wasn't much help anyway,
> the stuff I was interested in was pre-exception, and the backtrace
> seemed to stop at the exception handling (unlike when 'live' debugging
> when the stack trace continued).

Hmm..  That's probably a bug of some sort, since I think the two methods 
should produce the same results...

      reply	other threads:[~2021-12-30 15:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 23:10 Jeremy Drake
2021-12-24  0:06 ` Ken Brown
2021-12-24  0:29   ` Jeremy Drake
2021-12-24 17:17     ` Ken Brown
2021-12-24 19:42       ` Jeremy Drake
2021-12-24 22:46         ` Ken Brown
2021-12-24 23:42           ` Jeremy Drake
2021-12-25  0:39           ` Jeremy Drake
2021-12-25  3:19             ` Takashi Yano
2021-12-25  3:47               ` Jeremy Drake
2021-12-25  4:12                 ` Takashi Yano
2021-12-25  5:40                   ` Jeremy Drake
2021-12-25 17:10                     ` Takashi Yano
2021-12-25 17:16                       ` Takashi Yano
2021-12-25 19:00                         ` Marco Atzeri
2021-12-25 19:20                       ` Jeremy Drake
2021-12-25 22:18                         ` Ken Brown
2021-12-25 23:00                         ` Jeremy Drake
2021-12-26  3:04                           ` Ken Brown
2021-12-26  4:56                             ` Jeremy Drake
2021-12-26 15:09                               ` Ken Brown
2021-12-26 16:04                                 ` Ken Brown
2021-12-26 16:24                                   ` Ken Brown
2021-12-26 21:35                                     ` Jeremy Drake
2021-12-26 22:18                                       ` Ken Brown
2021-12-26 22:43                                         ` Jeremy Drake
2021-12-26 23:12                                           ` Ken Brown
2021-12-26 23:23                                             ` Jeremy Drake
2021-12-27  2:42                                               ` Ken Brown
2021-12-27 21:12                                                 ` Jeremy Drake
2021-12-29 21:59                                             ` Ken Brown
2021-12-29 23:29                                               ` Jeremy Drake
2021-12-27 20:01     ` Jon Turney
2021-12-29  5:45       ` Jeremy Drake
2021-12-30 15:44         ` Jon Turney [this message]

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=9796eaa8-07f1-0f14-3105-9ce482005b17@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-patches@cygwin.com \
    /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).