From: Ray Wells <vk2tv@exemail.com.au>
To: Bernard Pidoux F6BVP <f6bvp@free.fr>
Cc: Jose Ng Lee <jng@psi.net.pa>, linux-hams@vger.kernel.org
Subject: Re: fbbsrc.704r4-5 stack smashing
Date: Sat, 19 Sep 2009 06:47:32 +1000 [thread overview]
Message-ID: <4AB3F1E4.1030802@exemail.com.au> (raw)
In-Reply-To: <4AB38D4B.3010808@free.fr>
Hi Bernard,
No, I didn't. It was some months ago now, before you made that discovery.
I'm a bit tight for time right now with radio station administration but
when that finishes I'll try your test fbb.
Ray vk2tv
Bernard Pidoux F6BVP wrote:
> Hi Ray,
>
> Did you check if there were some held message files (
> /var/ax25/fbb/mail/*.hld )
> on your systems that were unable to start FBB BBS ?
>
> When I removed those files from w4akh-8 BBS, there was no more
> stack-smashing when xfbbd daemon was started.
>
> If there are some .hld files, this would confirm that initialization
> phase
> was buggy and were the cause of stack-smashing you had.
>
> However, don't remove the above files. Just rename them temporarily for
> the completion of your tests.
>
> I will release soon a new version that hopefully will correct this
> annoying bug.
>
> 73 de Bernard, f6bvp
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2009-09-18 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 0:00 fbbsrc.704r5 compile error Jose Ng Lee
2009-09-18 1:21 ` Dave Platt
2009-09-18 1:33 ` Ray Wells
2009-09-18 13:17 ` Bernard Pidoux F6BVP
[not found] ` <BC95AC1740034FE796CAA73C11319A31@HOLLYWOOD.HOLLYWOOD.COM>
2009-09-20 10:34 ` Bernard Pidoux F6BVP
2009-09-18 13:38 ` fbbsrc.704r4-5 stack smashing Bernard Pidoux F6BVP
2009-09-18 20:47 ` Ray Wells [this message]
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=4AB3F1E4.1030802@exemail.com.au \
--to=vk2tv@exemail.com.au \
--cc=f6bvp@free.fr \
--cc=jng@psi.net.pa \
--cc=linux-hams@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.