OpenWrt Forum Archive

Topic: possible problem in libpthread? ssmtp sigsegvs

The content of this topic has been archived on 12 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Post #1
frogzoo
2 Nov 2005, 03:04

Ssmtp which used to work for me, WR RC3, now sigsegvs, though the package hasn't changed.

Ergo, something else has broken it, my guess is libpthread?

last few lines of strace
<snip>
open("/etc/ssmtp/revaliases", O_RDONLY) = -1 ENOENT (No such file or directory)
read(0, "blah\n", 4096)                 = 5
read(0, "", 4096)                       = 0
rt_sigaction(SIGALRM, {0x10000000, [], SA_SIGINFO|0x404654}, {SIG_DFL}, 16) = 0
alarm(600)                              = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

Post #2
Nico
2 Nov 2005, 03:57

did you update your libopenssl / libpthread packages from stock whiterussian ?
if so, where did those new packages came from ?

Post #3
frogzoo
2 Nov 2005, 04:16

Nico,
only from wherever the makefiles/wget are pulling them smile

My bad anyway, just dl'd ssmtp 2-61-2 (latest) and compiles cleanly/runs no problems. Happy to build an updated package.

So next question, how do  you want the package, as a diff against source, or an ipkg?

Post #4
Nico
2 Nov 2005, 04:32
frogzoo wrote:

only from wherever the makefiles/wget are pulling them

so you are building from source... and mixing packages you built yourself with official ones...

frogzoo wrote:

My bad anyway, just dl'd ssmtp 2-61-2 (latest) and compiles cleanly/runs no problems. Happy to build an updated package.

Sure it will compile cleanly : http://packages.debian.org/changelogs/p … /changelog

frogzoo wrote:

So next question, how do  you want the package, as a diff against source, or an ipkg?

Developers are usually eating diffs, in unified format (diff -ruN)

The discussion might have continued from here.