public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Unable to open the clipboard
Date: Sat, 22 Jan 2022 00:35:17 -0800	[thread overview]
Message-ID: <0b92b1a2-2206-6022-cbf2-bdc870003ead@maxrnd.com> (raw)
In-Reply-To: <20e4a66c-476c-e059-81df-d85c2d3a8308@gmail.com>

Hi Marco,

Marco Atzeri wrote:
> On 10.01.2022 07:44, Mark Geisert wrote:
>>> Marco Atzeri wrote:
>>>> On 04.01.2022 19:08, Marco Atzeri wrote:
>>>>> On 04.01.2022 06:15, Mark Geisert wrote:
>>>>
>>>> Hi Mark,
>>>> just found another issue
>>>>
>>>> $ putclip < Announce_octave
>>>> Aborted (core dumped)
>>>>
>>>> It seems caused by the longest line (86 characters)
>>>>
>>>> $ cat Announce_octave  | putclip
>>>> Aborted (core dumped)
>>>>
>>>> $ cat Announce_octave | sed -e "/html$/ d" | putclip
>>>>
>>>> of course the Clipboard is fine
>>>>
>>>> $ cat Announce_octave  > /dev/clipboard
>>
>> I'm unable to reproduce.  If you happen to have a putclip.exe.stackdump left 
>> behind, could you post that please?
>>
>> ..mark
>>
> 
> here it is
> 
> $ cat putclip.exe.stackdump
> Stack trace:
> Frame        Function    Args
> 000FFFFB980  001800620B7 (000FFFFBB88, 00000000002, 00000000002, 000FFFFDE50)
> 00000000000  001800640F5 (00000000064, 00000000000, 00000000078, 00000000000)
> 000FFFFC090  001801305E8 (00100000080, 000007E67F0, 00000000000, 00000000000)
> 000000000C1  0018012BD1B (0000000001F, 00000000000, 00000000000, 0018022DE20)
> 00000000609  0018012C125 (7FF84F2EBA68, 000FFFFC420, 7FF84FA9FB43, 00000000000)
> 00000000609  00180212C08 (000FFFFC440, 00000000000, 00800000000, 13920028A3BD5C75)
> 00000000609  00180213065 (00000400028, 7FF84FA958B0, 7FF84FA95990, 00000400028)
> 00000000609  001800D7FE8 (00000000000, 00000400018, 00100000001, 00800000BB0)
> 00000000609  0018018EFFB (00000000000, 00000400018, 00100000001, 00800000BB0)
> 00000000609  0010040162C (37003600000002, EA8087F46D20, 7FF84EA653DC, 00000000000)
> 00000000000  0010040261E (00180049B21, 00180048A70, 00000000002, 00180322FC0)
> 000FFFFCD30  00180049B8D (00000000000, 00000000000, 00000000000, 00000000000)
> 000FFFFFFF0  00180047746 (00000000000, 00000000000, 00000000000, 00000000000)
> 000FFFFFFF0  001800477F4 (00000000000, 00000000000, 00000000000, 00000000000)
> End of stack trace

Thanks for that.  Just wanted to say I haven't forgotten about this report. 
Unlike previous putclip|getclip error reports, this one is a Heisenbug.. difficult 
to reproduce under a debugger or with any change made to the source.  I do have a 
handle on the issue thanks to a malloc debugger: it's a buffer overrun.  Debugging 
continues...

..mark

      reply	other threads:[~2022-01-22  8:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 14:34 Marco Atzeri
2022-01-03 15:59 ` Ken Brown
2022-01-03 17:47   ` Marco Atzeri
2022-01-04  0:25 ` Mark Geisert
2022-01-04  2:23   ` Marco Atzeri
2022-01-04  5:12     ` Mark Geisert
2022-01-04  5:15       ` Mark Geisert
2022-01-04 18:08         ` Marco Atzeri
2022-01-06  9:29           ` Marco Atzeri
2022-01-07  3:32             ` Mark Geisert
2022-01-10  6:44               ` Mark Geisert
2022-01-10  7:02                 ` Marco Atzeri
2022-01-22  8:35                   ` Mark Geisert [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=0b92b1a2-2206-6022-cbf2-bdc870003ead@maxrnd.com \
    --to=mark@maxrnd.com \
    --cc=cygwin@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).