Your message dated Sun, 18 Oct 2015 21:08:46 +0200 with message-id <[email protected]> and subject line Re: Bug#801638: libc-2.19.so: segfault at 0 ip 00000000f763946c sp 00000000ffe955e8 error 4 in libc-2.19.so[f74fb000+1a4000] has caused the Debian Bug report #801638, regarding libc-2.19.so: segfault at 0 ip 00000000f763946c sp 00000000ffe955e8 error 4 in libc-2.19.so[f74fb000+1a4000] to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 801638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801638 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libc6 Version: 2.19-18+deb8u1 Severity: normal File: libc-2.19.so Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldoldstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages libc6:amd64 depends on: ii libgcc1 1:4.9.2-10 libc6:amd64 recommends no packages. Versions of packages libc6:amd64 suggests: ii debconf [debconf-2.0] 1.5.56 pn glibc-doc <none> ii locales 2.19-18+deb8u1 -- debconf information: glibc/restart-services: glibc/disable-screensaver: glibc/restart-failed: glibc/upgrade: true libraries/restart-without-asking: false
--- End Message ---
--- Begin Message ---On 2015-10-18 19:44, Aurelien Jarno wrote: > On 2015-10-13 00:27, Segmentation fault wrote: > > Package: libc6 > > Version: 2.19-18+deb8u1 > > Severity: normal > > File: libc-2.19.so > > > > Dear Maintainer, > > > > *** Reporter, please consider answering these questions, where appropriate > > *** > > > > * What led up to the situation? > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > * What was the outcome of this action? > > * What outcome did you expect instead? > > The error message you report likely means that one of the libc functions > was wrongly passed a NULL pointer. As such it's a bug in the application > you used and not in the libc. Can you please consider answering the > above question, so that we can identify the broken application and > reassign the bug to it? In the contrary we'll simply close this bug in > the next days. I got the following error message when sending the mail. | This message was created automatically by mail delivery software. | | A message that you sent could not be delivered to one or more of its | recipients. This is a permanent error. The following address(es) failed: | | [email protected] | SMTP error from remote mail server after end of data: | host mxs.mail.ru [217.69.139.150]: 550 Message was not accepted -- invalid mailbox. Local mailbox [email protected] is unavailable: | account is disabled I am therefore closing the bug. Please reopen it if more details if the bug can be reproduced. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://www.aurel32.net
--- End Message ---
