From: Florian Weimer <fweimer@redhat.com>
To: Michael Brunnbauer <brunni@netestate.de>
Cc: libc-help@sourceware.org
Subject: Re: Old Python binary eats all mem after upgrade to 2.28
Date: Thu, 09 Aug 2018 08:39:00 -0000 [thread overview]
Message-ID: <c55e7746-1978-035b-d035-a8676c6b7381@redhat.com> (raw)
In-Reply-To: <20180809073231.GA24865@netestate.de>
On 08/09/2018 09:32 AM, Michael Brunnbauer wrote:
> Breakpoint 1, posix_listdir (self=0x0, args=0x80d542c)
> at ./Modules/posixmodule.c:1018
> 1018 in ./Modules/posixmodule.c
> (gdb) print ep
> $1 = (struct dirent *) 0x8103c0c
> (gdb) print ep->d_name
> $2 = "\000\207V\000\000\200\016\315\022\020\000\000..\000\000\000\034Z\000\000\200\264\265\026$\000\000_mysql_exceptions.pyc\000\000\000\000\035Z\000\000\200\362\034!\024\000\000README\000\000\000\036Z\000\000\200w\323\070 \000\000CompatMysqldb.pyc\000\000\000\000\037Z\000\000\200\240Y;\030\000\000_mysql.so\000\000\000\000 Z\000\000\200\370vT\024\000\000csv.so\000\000\000!Z\000\000\200\314\314^\034\000\000CompatMysqldb.py\000\"Z\000\000\000\276\332v \000\000_mysql_excep"...
> (gdb) continue 10
> Will ignore next 9 crossings of breakpoint 1. Continuing.
>
> Breakpoint 1, posix_listdir (self=0x0, args=0x80d542c)
> at ./Modules/posixmodule.c:1018
> 1018 in ./Modules/posixmodule.c
> (gdb) print ep
> $3 = (struct dirent *) 0x8103c0c
> (gdb) print ep->d_name
> $4 = "\000\207V\000\000\200\016\315\022\020\000\000..\000\000\000\034Z\000\000\200\264\265\026$\000\000_mysql_exceptions.pyc\000\000\000\000\035Z\000\000\200\362\034!\024\000\000README\000\000\000\036Z\000\000\200w\323\070 \000\000CompatMysqldb.pyc\000\000\000\000\037Z\000\000\200\240Y;\030\000\000_mysql.so\000\000\000\000 Z\000\000\200\370vT\024\000\000csv.so\000\000\000!Z\000\000\200\314\314^\034\000\000CompatMysqldb.py\000\"Z\000\000\000\276\332v \000\000_mysql_excep"...
This looks like the parser for the getdtents output getting
desynchronized. I don't remember anyone reporting anything like this
before.
I have an idea what might be going on. I'll try to write a test case to
reproduce this.
Thanks,
Florian
next prev parent reply other threads:[~2018-08-09 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 13:54 Michael Brunnbauer
2018-08-08 14:03 ` Michael Brunnbauer
2018-08-08 14:54 ` Florian Weimer
2018-08-08 20:23 ` Michael Brunnbauer
2018-08-09 6:27 ` Florian Weimer
2018-08-09 7:32 ` Michael Brunnbauer
2018-08-09 8:39 ` Florian Weimer [this message]
2018-08-09 9:21 ` Florian Weimer
2018-08-09 10:47 ` Michael Brunnbauer
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=c55e7746-1978-035b-d035-a8676c6b7381@redhat.com \
--to=fweimer@redhat.com \
--cc=brunni@netestate.de \
--cc=libc-help@sourceware.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.
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).