(fwd) Re: v2.1.107: Myterious segfault while sending mail.

Robert Broughton (roberb7@uniserve.com)
Fri, 24 Jul 1998 10:45:33 -0700 (PDT)

-- forwarded message --
Path: Supernews70!Supernews69!venn.bc.ca!not-for-mail
From: altnews@uniserve.com (Robert Broughton)
Newsgroups: muc.lists.linux-kernel
Subject: Re: v2.1.107: Myterious segfault while sending mail.
Date: 22 Jul 1998 15:02:21 GMT
Organization: Venn Software Ltd.
Lines: 78
Message-ID: <6p4utt$4ep$1@venn.bc.ca>
Reply-To: roberb7@uniserve.com
NNTP-Posting-Host: 204.244.163.50
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: 901120496 L1Y5MIKFTA332CCF4C usenet103.supernews.com
X-Complaints-To: newsabuse@supernews.com
X-Newsreader: knews 0.9.8
Cache-Post-Path: neptune.uniserve.com!unknown@van4d38.dial.uniserve.ca
X-Cache: nntpcache 2.3.2.1 (see http://www.nntpcache.org/)
Xref: Supernews70 muc.lists.linux-kernel:9663
X-Cache: nntpcache 2.3.2.1 (see http://www.nntpcache.org/)

In article <XFMail.980627061104.root@solfire.ludwigsburg.netsurf.de>,
root@solfire.ludwigsburg.netsurf.de (Meino Christian Cramer) writes:
>
> I use:
> sendmail 8.9.0
> fetchmail 4.5.0
> linux v.2.1.107
>

fetchmail 4.5.0
linux v2.1.86
glibc 2.0.6

> _Before_ I have sent mail I am able to retrieve mail via fetchmail
> without problems.

I can't retrive mail at all with fetchmail. (popclient works fine.)

> When I have send mail vial sendmail (sounds logical, hmmm) and THEN
> try to retrieve mail with fetchmail I simply get "segfault" regardless,
> whether I am "in X" or "on console".
>
> No trace in syslog or other logfiles.
>
> The only thing is a tracer file (via strace) which is too longish to send
> (but: I one wants it: NO problem -- please mail me directly!)
> The last lines of it are::
>
>
> fstat(4, {st_dev=makedev(8, 2), st_ino=74190, st_mode=S_IFREG|0600, st_nlink=1,
> st_uid=0, st_gid=0, st_blksize=4096, st_blocks=
> 8, st_size=3475, st_atime=98/06/27-05:59:56, st_mtime=97/06/21-21:08:22,
> st_ctime=98/04/22-18:20:58}) = 0
> mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x40008000
> read(4, "# fetchmail control file sample\n"..., 4096) = 3475
> read(4, "", 4096) = 0
> read(4, "", 4096) = 0
> ioctl(4, TCGETS, 0xbfffacc0) = -1 ENOTTY (Not a typewriter)
> close(4) = 0
> munmap(0x40008000, 4096) = 0
> --- SIGSEGV (Segmentation fault) ---
> +++ killed by SIGSEGV +++
>
>
> Any idea?
>
My strace looks like this:

setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={300, 0}}, NULL) = 0
recv(4, ".\r\n", 512, MSG_PEEK) = 3
read(4, ".\r\n", 3) = 3
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0
write(2, "3 messages for roberb7 at pop.un"..., 42) = 42
write(2, " (19804 bytes).", 15) = 15
write(2, "\n", 1) = 1
write(4, "RETR 1\r\n", 8) = 8
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={300, 0}}, NULL) = 0
recv(4, "+OK Message follows\r\nReturn-pa"..., 512, MSG_PEEK) = 512
read(4, "+OK Message follows\r\n", 21) = 21
setitimer(ITIMER_REAL, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0
write(2, "reading message 1 of 3", 22) = 22
write(2, " (2152 bytes)", 13) = 13
write(2, " ", 1) = 1
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

I took a different approach, using gdb rather than strace. gdb shows
that the segmentation fault occurs on a call to malloc, for 8193 bytes.

-- 
"I am a law abiding citizen, its the law that makes me a criminal!"
	-sschnurr@rogers.wave.ca


Bob Broughton
mailto:roberb7@uniserve.com
WWW: http://users.uniserve.com/~roberb7
Vancouver, BC, Canada
-- end of forwarded message --



-- 
-----
Robert Broughton		roberb7@uniserve.com


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html