Skip to contentSkip to conversation

Ubuntu 8.04 / 8.10

DISCUSSION Peter Mallett 5 participants 6 messages Feb 13, 2009

lore
Share & tools
lore
#0 lore raw

Hi All,

I have been trying different distro`s in the last few days and
they both gave the same results as below.

I have even tried to compile and run fbb 7.04r but this gave the same problems.

Has the above distro`s become broken for fbb ?

Quoted 32 lines

*** stack smashing detected ***: /usr/sbin/xfbbd terminated ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7e5e138] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb7e5e0f0] /usr/sbin/xfbbd[0x80855a3]
/usr/sbin/xfbbd[0x80856c5]
/usr/sbin/xfbbd[0x8083da5]
/usr/sbin/xfbbd[0x807e4ab]
/usr/sbin/xfbbd[0x80878d5]
/usr/sbin/xfbbd[0x804dbdc] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7d87450] /usr/sbin/xfbbd[0x804aa01]
======= Memory map: ========

08048000-080db000 r-xp 00000000 08:21 605287     /usr/sbin/xfbbd
080db000-080dd000 rw-p 00093000 08:21 605287     /usr/sbin/xfbbd
080dd000-08269000 rw-p 080dd000 00:00 0          [heap]
b7d1a000-b7d24000 r-xp 00000000 08:21 1403541    /lib/libgcc_s.so.1
b7d24000-b7d25000 rw-p 0000a000 08:21 1403541    /lib/libgcc_s.so.1
b7d31000-b7d70000 r--p 00000000 08:21 636870     /usr/lib/locale/en_NZ.utf8/LC_CTYPE
b7d70000-b7d71000 rw-p b7d70000 00:00 0
b7d71000-b7eba000 r-xp 00000000 08:21 1420840    /lib/tls/i686/cmov/libc-2.7.so
b7eba000-b7ebb000 r--p 00149000 08:21 1420840    /lib/tls/i686/cmov/libc-2.7.so
b7ebb000-b7ebd000 rw-p 0014a000 08:21 1420840    /lib/tls/i686/cmov/libc-2.7.so
b7ebd000-b7ec0000 rw-p b7ebd000 00:00 0
b7ec0000-b7ec7000 r-xp 00000000 08:21 605061     /usr/lib/libax25.so.0.0.0
b7ec7000-b7ec8000 rw-p 00007000 08:21 605061     /usr/lib/libax25.so.0.0.0
b7ec8000-b7eeb000 r-xp 00000000 08:21 1420844    /lib/tls/i686/cmov/libm-2.7.so
b7eeb000-b7eed000 rw-p 00023000 08:21 1420844    /lib/tls/i686/cmov/libm-2.7.so

b7eed000-b7eee000 rw-p b7eed000 00:00 0
b7ef1000-b7ef3000 rw-p b7ef1000 00:00 0
b7ef3000-b7efa000 r--s 00000000 08:21 612282 /usr/lib/gconv/gconv-modules.cache
b7efa000-b7efb000 rw-p b7efa000 00:00 0

Quoted 8 lines
b7efb000-b7efc000 r-xp b7efb000 00:00 0          [vdso]
b7efc000-b7f16000 r-xp 00000000 08:21 1403532    /lib/ld-2.7.so
b7f16000-b7f18000 rw-p 00019000 08:21 1403532    /lib/ld-2.7.so
bfccd000-bfce2000 rw-p bffeb000 00:00 0          [stack]

Aborted
Configuration error ! Giving up.
root@iGate:/etc/ax25#

Regards ..... Peter

#1 lore raw

Hi,

Have you tried adding
-fno-stack-protector to the gcc options in the makefile?

Have a look at the following thread.

http://ubuntuforums.org/showthread.php?t=418234

Regards
de John
EI7IG

Quoted 51 lines · Peter Mallett

Hi All,

I have been trying different distro`s in the last few days
and they both gave the same results as below.

I have even tried to compile and run fbb 7.04r but this gave the same problems.

Has the above distro`s become broken for fbb ?

Quoted 32 lines

*** stack smashing detected ***: /usr/sbin/xfbbd terminated ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7e5e138] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb7e5e0f0] /usr/sbin/xfbbd[0x80855a3]
/usr/sbin/xfbbd[0x80856c5]
/usr/sbin/xfbbd[0x8083da5]
/usr/sbin/xfbbd[0x807e4ab]
/usr/sbin/xfbbd[0x80878d5]
/usr/sbin/xfbbd[0x804dbdc] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7d87450] /usr/sbin/xfbbd[0x804aa01]
======= Memory map: ========

08048000-080db000 r-xp 00000000 08:21 605287     /usr/sbin/xfbbd
080db000-080dd000 rw-p 00093000 08:21 605287     /usr/sbin/xfbbd
080dd000-08269000 rw-p 080dd000 00:00 0          [heap]
b7d1a000-b7d24000 r-xp 00000000 08:21 1403541    /lib/libgcc_s.so.1
b7d24000-b7d25000 rw-p 0000a000 08:21 1403541    /lib/libgcc_s.so.1
b7d31000-b7d70000 r--p 00000000 08:21 636870     /usr/lib/locale/en_NZ.utf8/LC_CTYPE
b7d70000-b7d71000 rw-p b7d70000 00:00 0
b7d71000-b7eba000 r-xp 00000000 08:21 1420840    /lib/tls/i686/cmov/libc-2.7.so
b7eba000-b7ebb000 r--p 00149000 08:21 1420840    /lib/tls/i686/cmov/libc-2.7.so
b7ebb000-b7ebd000 rw-p 0014a000 08:21 1420840    /lib/tls/i686/cmov/libc-2.7.so
b7ebd000-b7ec0000 rw-p b7ebd000 00:00 0
b7ec0000-b7ec7000 r-xp 00000000 08:21 605061     /usr/lib/libax25.so.0.0.0
b7ec7000-b7ec8000 rw-p 00007000 08:21 605061     /usr/lib/libax25.so.0.0.0
b7ec8000-b7eeb000 r-xp 00000000 08:21 1420844    /lib/tls/i686/cmov/libm-2.7.so
b7eeb000-b7eed000 rw-p 00023000 08:21 1420844    /lib/tls/i686/cmov/libm-2.7.so

b7eed000-b7eee000 rw-p b7eed000 00:00 0
b7ef1000-b7ef3000 rw-p b7ef1000 00:00 0
b7ef3000-b7efa000 r--s 00000000 08:21 612282 /usr/lib/gconv/gconv-modules.cache
b7efa000-b7efb000 rw-p b7efa000 00:00 0

Quoted 8 lines
b7efb000-b7efc000 r-xp b7efb000 00:00 0          [vdso]
b7efc000-b7f16000 r-xp 00000000 08:21 1403532    /lib/ld-2.7.so
b7f16000-b7f18000 rw-p 00019000 08:21 1403532    /lib/ld-2.7.so
bfccd000-bfce2000 rw-p bffeb000 00:00 0          [stack]

Aborted
Configuration error ! Giving up.
root@iGate:/etc/ax25#

Quoted 7 lines

Regards ..... Peter

--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
John Ronan <[email protected]>, +353-51-302938 Telecommunications Software & Systems Group, http://www.tssg.org

#2 lore raw
In reply to Peter Mallett

Peter,

This problem arose with fbb around kernel 2.6.20 (can't remember just which one now)

The fix I apply is to compile fbb with -fno-stack-protection added to its Makefile. I don't have a fix if you install fbb from a deb package.

It seems that stack protection was included in kernels as a security plug for stack overflow.

I sent quite a bit about this to the xfbb list around 18 months ago.

Ray vk2tv

Quoted 58 lines · Peter Mallett

Hi All,

I have been trying different distro`s in the last few days and
they both gave the same results as below.

I have even tried to compile and run fbb 7.04r but this gave the same problems.

Has the above distro`s become broken for fbb ?

Quoted 32 lines

*** stack smashing detected ***: /usr/sbin/xfbbd terminated ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7e5e138] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb7e5e0f0] /usr/sbin/xfbbd[0x80855a3]
/usr/sbin/xfbbd[0x80856c5]
/usr/sbin/xfbbd[0x8083da5]
/usr/sbin/xfbbd[0x807e4ab]
/usr/sbin/xfbbd[0x80878d5]
/usr/sbin/xfbbd[0x804dbdc] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7d87450] /usr/sbin/xfbbd[0x804aa01]
======= Memory map: ========

08048000-080db000 r-xp 00000000 08:21 605287     /usr/sbin/xfbbd
080db000-080dd000 rw-p 00093000 08:21 605287     /usr/sbin/xfbbd
080dd000-08269000 rw-p 080dd000 00:00 0          [heap]
b7d1a000-b7d24000 r-xp 00000000 08:21 1403541    /lib/libgcc_s.so.1
b7d24000-b7d25000 rw-p 0000a000 08:21 1403541    /lib/libgcc_s.so.1
b7d31000-b7d70000 r--p 00000000 08:21 636870     /usr/lib/locale/en_NZ.utf8/LC_CTYPE
b7d70000-b7d71000 rw-p b7d70000 00:00 0
b7d71000-b7eba000 r-xp 00000000 08:21 1420840    /lib/tls/i686/cmov/libc-2.7.so
b7eba000-b7ebb000 r--p 00149000 08:21 1420840    /lib/tls/i686/cmov/libc-2.7.so
b7ebb000-b7ebd000 rw-p 0014a000 08:21 1420840    /lib/tls/i686/cmov/libc-2.7.so
b7ebd000-b7ec0000 rw-p b7ebd000 00:00 0
b7ec0000-b7ec7000 r-xp 00000000 08:21 605061     /usr/lib/libax25.so.0.0.0
b7ec7000-b7ec8000 rw-p 00007000 08:21 605061     /usr/lib/libax25.so.0.0.0
b7ec8000-b7eeb000 r-xp 00000000 08:21 1420844    /lib/tls/i686/cmov/libm-2.7.so
b7eeb000-b7eed000 rw-p 00023000 08:21 1420844    /lib/tls/i686/cmov/libm-2.7.so

b7eed000-b7eee000 rw-p b7eed000 00:00 0
b7ef1000-b7ef3000 rw-p b7ef1000 00:00 0
b7ef3000-b7efa000 r--s 00000000 08:21 612282 /usr/lib/gconv/gconv-modules.cache
b7efa000-b7efb000 rw-p b7efa000 00:00 0

Quoted 8 lines
b7efb000-b7efc000 r-xp b7efb000 00:00 0          [vdso]
b7efc000-b7f16000 r-xp 00000000 08:21 1403532    /lib/ld-2.7.so
b7f16000-b7f18000 rw-p 00019000 08:21 1403532    /lib/ld-2.7.so
bfccd000-bfce2000 rw-p bffeb000 00:00 0          [stack]

Aborted
Configuration error ! Giving up.
root@iGate:/etc/ax25#

Regards ..... Peter

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw
Quoted 9 lines · Ray Wells

Peter,

This problem arose with fbb around kernel 2.6.20 (can't remember just which one now)

The fix I apply is to compile fbb with -fno-stack-protection added to its Makefile. I don't have a fix if you install fbb from a deb package.

It seems that stack protection was included in kernels as a security plug for stack overflow.

I sent quite a bit about this to the xfbb list around 18 months ago.

The real question (to me at least) is whether the stack-smash abort is a false alarm, or whether it indicates a real problem in the FBB software.

If there really is a way in which the FBB software is managing to smash its own stack (via e.g. a buffer that's too small, indexing out of bounds, etc.), then simply disabling the stack protection feature via recompilation is a bit like replacing a blown fuse with a larger one. You may get away with it, or it may burn your house down :-(

It'd probably be necessary to compile xfbb with -g and run it under GDB or a similar debugger, and investigate the state of the stack at the time of the abort, to figure out what's being over-written.

#4 lore raw
Quoted 6 lines · Dave Platt

If there really is a way in which the FBB software is managing to smash its own stack (via e.g. a buffer that's too small, indexing out of bounds, etc.), then simply disabling the stack protection feature via recompilation is a bit like replacing a blown fuse with a larger one. You may get away with it, or it may burn your house down :-(

Naw, more like replacing a blown fuse with a .22 bullet!

Yes, it's been done...

Signature · 5 lines
Curt, WE7U.				archer at eskimo dot com
http://www.eskimo.com/~archer
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"
#5 lore raw
In reply to Dave Platt
Quoted 22 lines · Dave Platt
Quoted 9 lines · Ray Wells

Peter,

This problem arose with fbb around kernel 2.6.20 (can't remember just which one now)

The fix I apply is to compile fbb with -fno-stack-protection added to its Makefile. I don't have a fix if you install fbb from a deb package.

It seems that stack protection was included in kernels as a security plug for stack overflow.

I sent quite a bit about this to the xfbb list around 18 months ago.

The real question (to me at least) is whether the stack-smash abort is a false alarm, or whether it indicates a real problem in the FBB software.

If there really is a way in which the FBB software is managing to smash its own stack (via e.g. a buffer that's too small, indexing out of bounds, etc.), then simply disabling the stack protection feature via recompilation is a bit like replacing a blown fuse with a larger one. You may get away with it, or it may burn your house down :-(

Quoted 9 lines

It'd probably be necessary to compile xfbb with -g and run it under GDB or a similar debugger, and investigate the state of the stack at the time of the abort, to figure out what's being over-written.

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

The logic I applied at the time was that since fbb had always been broken (but not previously detected) I wasn't going to break it any more by disabling stack protection. I've certainly not detected any problems with fbb since I started doing this. If somebody with c programming skills wants to fix the real problem, we will welcome you with open arms, but I don't have those skills and I do need to keep the bbs functioning. I have achieved that target.

Ray vk2tv