Debian Bug report logs - #801665
bashdb: set0 and readc builtins do not build on non-linux

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Nicholas Bamber <nicholas@periapt.co.uk>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: bashdb: set0 and readc builtins do not build on non-linux

Date: Tue, 13 Oct 2015 09:48:49 +0100

Package: bashdb
Version: 4.3.0.91+ds-4
Severity: minor

Dear Maintainer,

bashdb 4.3.0.91+ds-4 only builds on mon-linux because we turn
off compiling set0 and readc. They compile but fail to load.

There are three potential sources of the problem:
1. The set0.c and readc.c code.
2. The headers supplied by the bash-builtins package
3. Some inadequacies on the non-linux platform.

So I ran this experiment that points to the issue being 1. It can be reproduced
using the followig steps:

cp /usr/share/doc/bash-builtins/examples/loadables/hello.c .
gcc -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2 -I /usr/include/bash/ -I /usr/include/bash//include -I/usr/include/bash//builtins  -fPIC -DPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o hello-hello.o `test -f 'hello.c' || echo './'`hello.c 
gcc  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -o hello \
	-shared hello-hello.o  
enable -f ./hello hello
hello

This should print "hello world" and it works on both linux and kfreebsd. So by trisecting the 
difference between hello.c on the one hand and set0.c/readc.c on the other we should 
be able to locate here the issue is. 

Versions of packages bashdb depends on:
ii  bash          4.3-11+b1
ii  libc6         2.19-18+deb8u1
ii  libreadline6  6.3-8+b3
ii  python        2.7.9-1

bashdb recommends no packages.

bashdb suggests no packages.

-- no debconf information

Message #16 received at 801665@bugs.debian.org (full text, mbox, reply):

From: Nicholas Bamber <nicholas@periapt.co.uk>

To: 801665@bugs.debian.org, control@bugs.debian.org

Subject: further info

Date: Wed, 14 Oct 2015 11:59:27 +0100

tag 801665 +help
reassign 801665 src:bashdb
thanks
user debian-bsd@lists.debian.org
usertag 801665 kfreebsd
thanks


The error on Debian kfreebsd for set0 is as follows:

-/«BUILDDIR»/bashdb-4.3.0.91+ds/command/set_sub/dollar0.sh: line 23: 
enable: cannot open shared object 
/«BUILDDIR»/bashdb-4.3.0.91+ds/builtin/set0: 
/«BUILDDIR»/bashdb-4.3.0.91+ds/builtin/set0: undefined symbol: dollar_vars


The issue in set0 is the dollar_vars variable from variables.c

/* Some funky variables which are known about specially.  Here is where
   "$*", "$1", and all the cruft is kept. */
char *dollar_vars[10];


For readc it appears to be terminate_immediately from sig.c.

/* When non-zero, we call the terminating signal handler immediately. */
int terminate_immediately = 0;


So it seems that on non-linux platforms bash has difficulty loading the 
compiled builtins IF those builtins reference data defined in the bash 
binary itself.

Message #23 received at 801665-done@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 801665-done@bugs.debian.org,820142-done@bugs.debian.org,839332-done@bugs.debian.org,

Cc: bashdb@packages.debian.org, bashdb@packages.qa.debian.org

Subject: Bug#870992: Removed package(s) from unstable

Date: Sun, 10 Sep 2017 16:06:31 +0000

Version: 4.3.0.91+ds-4+rm

Dear submitter,

as the package bashdb has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870992

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Send a report that this bug log contains spam.