unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Fernando de Morais <fernandodemorais.jf@gmail.com>
To: "J.P." <jp@neverwas.me>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
	emacs-erc@gnu.org, bandali@gnu.org, 54458@debbugs.gnu.org
Subject: bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow
Date: Sun, 03 Apr 2022 14:20:47 -0300	[thread overview]
Message-ID: <87h77aozgw.fsf@gmail.com> (raw)
In-Reply-To: <87sfqygccz.fsf@neverwas.me> (J. P.'s message of "Thu, 31 Mar 2022 12:18:04 -0700")

"J.P." <jp@neverwas.me> writes:

> Fernando,
>
> Please forget about the packet-capture thing. Setting that up and poring
> over the results is kind of a drag. As far as trying out patches,
> there's certainly no rush. While I'm sure you're probably all set,
> others wanting to play along may need a hand. I'm no Arch Linux wiz, but
> these steps have worked for me in the past:

Hello J.P.,

Sorry for the late response.

I applied your latest patch (0002) and file transfers larger than
120~150 MB, as well as much larger ones, completed successfully!

The only different behaviors I noticed in Emacs was the fact that it
stops responding when transfers go beyond a certain percentage of
completion (I couldn't be sure of the number, but in my experiments it
happens above 45%) and the impossibility of transferring more than one
file at the same time.

Other than that, transfers go as expected.

Thank you! I'll be using this patched version of `erc-dcc-get-filter'.

···

Mattias Engdegård <mattiase@acm.org> writes:

> Very useful! If I'm reading the stack trace right then someone should
> tell ERC not to send data from a process filter function:

Hi Mattias,

Thank you too, and just like J.P. wrote in his previous message, your
observations have been fundamental to solving the problem!

-- 
Regards,
Fernando de Morais.





  parent reply	other threads:[~2022-04-03 17:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 22:59 bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow Fernando de Morais
2022-03-21 14:09 ` J.P.
2022-03-22 13:50   ` Fernando de Morais
2022-03-22 14:36     ` Eli Zaretskii
     [not found]       ` <87tubj1eq4.fsf@gmail.com>
2022-03-27 17:56         ` Eli Zaretskii
2022-03-27 22:09           ` Fernando de Morais
2022-03-27 20:54 ` Mattias Engdegård
2022-03-28  9:23   ` Mattias Engdegård
2022-03-28 11:14     ` Eli Zaretskii
2022-03-28 12:08       ` J.P.
2022-03-29 15:49         ` Mattias Engdegård
2022-03-29 16:45           ` Eli Zaretskii
2022-03-29 17:47             ` Mattias Engdegård
2022-03-29 19:44               ` J.P.
2022-03-30  4:02                 ` J.P.
     [not found]                 ` <87mth8rst7.fsf@neverwas.me>
2022-03-30 15:28                   ` Mattias Engdegård
2022-03-31 19:18                     ` J.P.
     [not found]                     ` <87sfqygccz.fsf@neverwas.me>
2022-04-03 17:20                       ` Fernando de Morais [this message]
2022-04-03 19:46                         ` J.P.
     [not found]                         ` <87wng67xxd.fsf@neverwas.me>
2022-04-10 21:31                           ` J.P.
     [not found]                           ` <875yng39sa.fsf@neverwas.me>
2022-04-11  3:17                             ` J.P.
     [not found]                             ` <87sfqkz4ts.fsf@neverwas.me>
2022-04-25  0:59                               ` Fernando de Morais
     [not found]                               ` <87ilqyrn9s.fsf@gmail.com>
2022-04-25 12:08                                 ` J.P.
     [not found]                                 ` <878rrtz7or.fsf@neverwas.me>
2022-04-29 14:51                                   ` Fernando de Morais
     [not found]                                   ` <87r15guen2.fsf@gmail.com>
2022-04-30 13:39                                     ` J.P.
     [not found]                                     ` <87ilqqy9km.fsf@neverwas.me>
2022-05-04 13:03                                       ` Fernando de Morais
     [not found]                                       ` <87pmkth2lr.fsf@gmail.com>
2022-05-06 13:06                                         ` J.P.
     [not found]                                         ` <874k22zu7s.fsf@neverwas.me>
2022-05-08  1:16                                           ` Fernando de Morais
     [not found]                                           ` <87sfpk4ydj.fsf@gmail.com>
2022-05-11 14:29                                             ` J.P.
     [not found]                                             ` <87ee10xhw3.fsf@neverwas.me>
2022-05-23  1:22                                               ` J.P.
2022-04-01  6:32                   ` J.P.

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87h77aozgw.fsf@gmail.com \
    --to=fernandodemorais.jf@gmail.com \
    --cc=54458@debbugs.gnu.org \
    --cc=bandali@gnu.org \
    --cc=emacs-erc@gnu.org \
    --cc=jp@neverwas.me \
    --cc=mattiase@acm.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).