You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(9) |
Oct
(15) |
Nov
(6) |
Dec
(10) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
|
Feb
(5) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
(30) |
Sep
(4) |
Oct
(2) |
Nov
(4) |
Dec
|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(14) |
Jun
(2) |
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2005 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(2) |
2006 |
Jan
(10) |
Feb
(5) |
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
(6) |
Aug
(13) |
Sep
(1) |
Oct
|
Nov
|
Dec
(9) |
2007 |
Jan
(4) |
Feb
(11) |
Mar
(1) |
Apr
(5) |
May
(3) |
Jun
|
Jul
(6) |
Aug
(2) |
Sep
|
Oct
(2) |
Nov
(4) |
Dec
(1) |
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(9) |
Sep
(1) |
Oct
(7) |
Nov
|
Dec
(4) |
2009 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
(2) |
Aug
(3) |
Sep
(4) |
Oct
(3) |
Nov
(1) |
Dec
(2) |
2014 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2015 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(6) |
2017 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(5) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: R. B. <ro...@pa...> - 2008-10-20 01:28:17
|
In preparation for a release around October 27th, I've put a tarball on sourceforge which you can get at via http://bashdb.sf.net/libcdio-0.81cvs.tar.gz Please try out and let me know if there is a problem. Thanks. |
From: R. B. <ro...@pa...> - 2008-10-20 01:16:38
|
In preparation for a release around October 27th, I've put a tarball on sourceforge which you can get at via http://bashdb.sf.net/bashdb-4.0-cvs.tar.gz Please try out and let me know if there is a problem. Thanks. |
From: Masatake Y. <ya...@re...> - 2008-10-15 08:30:17
|
I got no answer, so I'll send again. Hi, To improve bashdb, a bash debugger, we submitted two patches to bash, adding readfile builtin and removing bashdb.el ever. I hope you don't forget it:) We would like submit one more patch, adding set0 builtin. The purpose of set0 in the debugger is that users often write programs that refer to $0. For example to display a usage string or maybe they change the behavior based on how they were called. So this helps in making these programs act the same way and gives an alternative to invoking with "bash --debugger". The patch is for the latest bash-3.2 patch level 039. We hope set0 is included in next version of bash. Regards, Masatake YAMATO diff -ruN bash-3.2-patched/builtins/Makefile.in bash-3.2-work/builtins/Makefile.in --- bash-3.2-patched/builtins/Makefile.in 2006-03-08 04:42:33.000000000 +0900 +++ bash-3.2-work/builtins/Makefile.in 2008-09-17 20:09:33.000000000 +0900 @@ -121,7 +121,7 @@ $(CC) -c $(CCFLAGS) $< DEFSRC = $(srcdir)/alias.def $(srcdir)/bind.def $(srcdir)/break.def \ - $(srcdir)/builtin.def $(srcdir)/caller.def \ + $(srcdir)/builtin.def $(srcdir)/caller.def $(srcdir)/set0.def \ $(srcdir)/cd.def $(srcdir)/colon.def \ $(srcdir)/command.def $(srcdir)/declare.def $(srcdir)/echo.def \ $(srcdir)/enable.def $(srcdir)/eval.def $(srcdir)/getopts.def \ @@ -140,7 +140,7 @@ getopt.h OFILES = builtins.o \ - alias.o bind.o break.o builtin.o caller.o cd.o colon.o command.o \ + alias.o bind.o break.o builtin.o caller.o set0.o cd.o colon.o command.o \ common.o declare.o echo.o enable.o eval.o evalfile.o \ evalstring.o exec.o \ exit.o fc.o fg_bg.o hash.o help.o history.o jobs.o kill.o let.o \ @@ -243,6 +243,7 @@ break.o: break.def builtin.o: builtin.def caller.o: caller.def +set0.o: set0.def cd.o: cd.def colon.o: colon.def command.o: command.def @@ -362,6 +363,12 @@ caller.o: $(topdir)/shell.h $(topdir)/syntax.h $(topdir)/unwind_prot.h $(topdir)/variables.h $(topdir)/conftypes.h caller.o: $(srcdir)/common.h $(BASHINCDIR)/maxpath.h ./builtext.h caller.o: ${BASHINCDIR}/chartypes.h $(topdir)/bashtypes.h +set0.o: $(topdir)/command.h ../config.h $(BASHINCDIR)/memalloc.h +set0.o: $(topdir)/general.h $(topdir)/xmalloc.h $(topdir)/quit.h $(topdir)/dispose_cmd.h +set0.o: $(topdir)/make_cmd.h $(topdir)/subst.h $(topdir)/externs.h +set0.o: $(topdir)/shell.h $(topdir)/syntax.h $(topdir)/unwind_prot.h $(topdir)/variables.h $(topdir)/conftypes.h +set0.o: $(srcdir)/common.h $(BASHINCDIR)/maxpath.h ./builtext.h +set0.o: ${BASHINCDIR}/chartypes.h $(topdir)/bashtypes.h cd.o: $(topdir)/command.h ../config.h $(BASHINCDIR)/memalloc.h $(topdir)/error.h cd.o: $(topdir)/general.h $(topdir)/xmalloc.h $(topdir)/quit.h $(topdir)/dispose_cmd.h cd.o: $(topdir)/make_cmd.h $(topdir)/subst.h $(topdir)/externs.h @@ -591,6 +598,7 @@ bind.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h break.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h caller.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h +set0.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h cd.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h common.c: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h complete.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h diff -ruN bash-3.2-patched/builtins/set0.def bash-3.2-work/builtins/set0.def --- bash-3.2-patched/builtins/set0.def 1970-01-01 09:00:00.000000000 +0900 +++ bash-3.2-work/builtins/set0.def 2008-09-17 20:31:42.000000000 +0900 @@ -0,0 +1,82 @@ +This file is caller.def, from which is created caller.c. It implements the +builtin "caller" in Bash. + +Copyright (C) 2008 Rocky Bernstein for Free Software Foundation, Inc. + +This file is part of GNU Bash, the Bourne Again SHell. + +Bash is free software; you can redistribute it and/or modify it under +the terms of the GNU General Public License as published by the Free +Software Foundation; either version 2, or (at your option) any later +version. + +Bash is distributed in the hope that it will be useful, but WITHOUT ANY +WARRANTY; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License +for more details. + +You should have received a copy of the GNU General Public License along +with Bash; see the file COPYING. If not, write to the Free Software +Foundation, 59 Temple Place, Suite 330, Boston, MA 02111 USA. + +$PRODUCES set0.c + +$BUILTIN set0 +$FUNCTION set0_builtin +$DEPENDS_ON DEBUGGER +$SHORT_DOC set0 STRING + +Set $0, the program name. +$END + +#include <config.h> + +#include "../bashintl.h" + +#include "../shell.h" +#include "common.h" + +#ifdef LOADABLE_BUILTIN +# include "builtins.h" +#endif + +int +set0_builtin (WORD_LIST *list) +{ + /* Check parameters: there should be exactly one. */ + if (list == 0) + { + builtin_error (_("An argument (a variable name) is required.")); + builtin_usage (); + return (EX_USAGE); + } + else if (list->next) + { + builtin_error (_("More than one argument passed; we want exactly one.")); + builtin_usage (); + return (EX_USAGE); + } + + if (dollar_vars[0]) + free (dollar_vars[0]); + dollar_vars[0] = savestring(list->word->word); + + return EXECUTION_SUCCESS; +} + +#ifdef LOADABLE_BUILTIN +static char *set0_doc[] = { + N_("Set $0, the program name."), + (char *)NULL +}; + +struct builtin set0_struct = { + "set0", /* builtin name */ + set0_builtin, /* function implementing the builtin */ + BUILTIN_ENABLED, /* initial flags for builtin */ + set0_doc, /* array of long documentation strings. */ + "set0 STRING", /* usage synopsis; becomes short_doc */ + 0 /* reserved for internal use */ +}; + +#endif /* LOADABLE_BUILTIN */ diff -ruN bash-3.2-patched/doc/bash.1 bash-3.2-work/doc/bash.1 --- bash-3.2-patched/doc/bash.1 2008-09-10 15:39:53.000000000 +0900 +++ bash-3.2-work/doc/bash.1 2008-09-17 20:31:04.000000000 +0900 @@ -7863,6 +7863,9 @@ The return status is always true unless an invalid option is encountered. .RE .TP +\fBset0\fP \fIstring\fP +Set \fB$0\fP, the program name. +.TP \fBshift\fP [\fIn\fP] The positional parameters from \fIn\fP+1 ... are renamed to .B $1 diff -ruN bash-3.2-patched/doc/bashref.texi bash-3.2-work/doc/bashref.texi --- bash-3.2-patched/doc/bashref.texi 2008-09-10 15:39:53.000000000 +0900 +++ bash-3.2-work/doc/bashref.texi 2008-09-17 20:34:18.000000000 +0900 @@ -2885,6 +2885,13 @@ The return status is non-zero if @code{return} is used outside a function and not during the execution of a script by @code{.} or @code{source}. +@item set0 +@btindex set0 +@example +set0 @var{string} +@end example +Set @code{$0}, the program name. + @item shift @btindex shift @example |
From: R. B. <ro...@pa...> - 2008-10-14 14:43:33
|
My current plan is to release bashdb 4.0 around October 27th. This is major rewrite in conjunction with work done for debuggers for ksh and zsh. I've tested this with bash 3.2 and 4.0 alpha. Many bugs have been fixed and I've started adding unit tests. (Unit tests are shorter, faster, more functional tests as opposed to the more complete "integration" tests). The help system is now much more like other debuggers I've worked on, namely pydb and ruby-debug: lists of the commands are appear as sorted list of columns. One incompatible change is that "short" commands are no longer hard-coded but are now "aliases" of longer command names. That means they can be unaliased and you can use them more easily as autoeval'd commands. Note: gdb doesn't have "aliases" but "macros". One new cool command I use a bit for debugging the debugger is the ability to turn xtrace on or off for a given function. Later on I'll make candidate releases. However I invite people to try what is in CVS and give feedback. Thanks. |
From: Masatake Y. <ya...@re...> - 2008-09-17 11:51:05
|
Hi, To improve bashdb, a bash debugger, we submitted two patches to bash, adding readfile builtin and removing bashdb.el ever. I hope you don't forget it:) We would like submit one more patch, adding set0 builtin. The purpose of set0 in the debugger is that users often write programs that refer to $0. For example to display a usage string or maybe they change the behavior based on how they were called. So this helps in making these programs act the same way and gives an alternative to invoking with "bash --debugger". The patch is for the latest bash-3.2 patch level 039. We hope set0 is included in next version of bash. Regards, Masatake YAMATO diff -ruN bash-3.2-patched/builtins/Makefile.in bash-3.2-work/builtins/Makefile.in --- bash-3.2-patched/builtins/Makefile.in 2006-03-08 04:42:33.000000000 +0900 +++ bash-3.2-work/builtins/Makefile.in 2008-09-17 20:09:33.000000000 +0900 @@ -121,7 +121,7 @@ $(CC) -c $(CCFLAGS) $< DEFSRC = $(srcdir)/alias.def $(srcdir)/bind.def $(srcdir)/break.def \ - $(srcdir)/builtin.def $(srcdir)/caller.def \ + $(srcdir)/builtin.def $(srcdir)/caller.def $(srcdir)/set0.def \ $(srcdir)/cd.def $(srcdir)/colon.def \ $(srcdir)/command.def $(srcdir)/declare.def $(srcdir)/echo.def \ $(srcdir)/enable.def $(srcdir)/eval.def $(srcdir)/getopts.def \ @@ -140,7 +140,7 @@ getopt.h OFILES = builtins.o \ - alias.o bind.o break.o builtin.o caller.o cd.o colon.o command.o \ + alias.o bind.o break.o builtin.o caller.o set0.o cd.o colon.o command.o \ common.o declare.o echo.o enable.o eval.o evalfile.o \ evalstring.o exec.o \ exit.o fc.o fg_bg.o hash.o help.o history.o jobs.o kill.o let.o \ @@ -243,6 +243,7 @@ break.o: break.def builtin.o: builtin.def caller.o: caller.def +set0.o: set0.def cd.o: cd.def colon.o: colon.def command.o: command.def @@ -362,6 +363,12 @@ caller.o: $(topdir)/shell.h $(topdir)/syntax.h $(topdir)/unwind_prot.h $(topdir)/variables.h $(topdir)/conftypes.h caller.o: $(srcdir)/common.h $(BASHINCDIR)/maxpath.h ./builtext.h caller.o: ${BASHINCDIR}/chartypes.h $(topdir)/bashtypes.h +set0.o: $(topdir)/command.h ../config.h $(BASHINCDIR)/memalloc.h +set0.o: $(topdir)/general.h $(topdir)/xmalloc.h $(topdir)/quit.h $(topdir)/dispose_cmd.h +set0.o: $(topdir)/make_cmd.h $(topdir)/subst.h $(topdir)/externs.h +set0.o: $(topdir)/shell.h $(topdir)/syntax.h $(topdir)/unwind_prot.h $(topdir)/variables.h $(topdir)/conftypes.h +set0.o: $(srcdir)/common.h $(BASHINCDIR)/maxpath.h ./builtext.h +set0.o: ${BASHINCDIR}/chartypes.h $(topdir)/bashtypes.h cd.o: $(topdir)/command.h ../config.h $(BASHINCDIR)/memalloc.h $(topdir)/error.h cd.o: $(topdir)/general.h $(topdir)/xmalloc.h $(topdir)/quit.h $(topdir)/dispose_cmd.h cd.o: $(topdir)/make_cmd.h $(topdir)/subst.h $(topdir)/externs.h @@ -591,6 +598,7 @@ bind.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h break.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h caller.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h +set0.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h cd.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h common.c: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h complete.o: ${topdir}/bashintl.h ${LIBINTL_H} $(BASHINCDIR)/gettext.h diff -ruN bash-3.2-patched/builtins/set0.def bash-3.2-work/builtins/set0.def --- bash-3.2-patched/builtins/set0.def 1970-01-01 09:00:00.000000000 +0900 +++ bash-3.2-work/builtins/set0.def 2008-09-17 20:31:42.000000000 +0900 @@ -0,0 +1,82 @@ +This file is caller.def, from which is created caller.c. It implements the +builtin "caller" in Bash. + +Copyright (C) 2008 Rocky Bernstein for Free Software Foundation, Inc. + +This file is part of GNU Bash, the Bourne Again SHell. + +Bash is free software; you can redistribute it and/or modify it under +the terms of the GNU General Public License as published by the Free +Software Foundation; either version 2, or (at your option) any later +version. + +Bash is distributed in the hope that it will be useful, but WITHOUT ANY +WARRANTY; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License +for more details. + +You should have received a copy of the GNU General Public License along +with Bash; see the file COPYING. If not, write to the Free Software +Foundation, 59 Temple Place, Suite 330, Boston, MA 02111 USA. + +$PRODUCES set0.c + +$BUILTIN set0 +$FUNCTION set0_builtin +$DEPENDS_ON DEBUGGER +$SHORT_DOC set0 STRING + +Set $0, the program name. +$END + +#include <config.h> + +#include "../bashintl.h" + +#include "../shell.h" +#include "common.h" + +#ifdef LOADABLE_BUILTIN +# include "builtins.h" +#endif + +int +set0_builtin (WORD_LIST *list) +{ + /* Check parameters: there should be exactly one. */ + if (list == 0) + { + builtin_error (_("An argument (a variable name) is required.")); + builtin_usage (); + return (EX_USAGE); + } + else if (list->next) + { + builtin_error (_("More than one argument passed; we want exactly one.")); + builtin_usage (); + return (EX_USAGE); + } + + if (dollar_vars[0]) + free (dollar_vars[0]); + dollar_vars[0] = savestring(list->word->word); + + return EXECUTION_SUCCESS; +} + +#ifdef LOADABLE_BUILTIN +static char *set0_doc[] = { + N_("Set $0, the program name."), + (char *)NULL +}; + +struct builtin set0_struct = { + "set0", /* builtin name */ + set0_builtin, /* function implementing the builtin */ + BUILTIN_ENABLED, /* initial flags for builtin */ + set0_doc, /* array of long documentation strings. */ + "set0 STRING", /* usage synopsis; becomes short_doc */ + 0 /* reserved for internal use */ +}; + +#endif /* LOADABLE_BUILTIN */ diff -ruN bash-3.2-patched/doc/bash.1 bash-3.2-work/doc/bash.1 --- bash-3.2-patched/doc/bash.1 2008-09-10 15:39:53.000000000 +0900 +++ bash-3.2-work/doc/bash.1 2008-09-17 20:31:04.000000000 +0900 @@ -7863,6 +7863,9 @@ The return status is always true unless an invalid option is encountered. .RE .TP +\fBset0\fP \fIstring\fP +Set \fB$0\fP, the program name. +.TP \fBshift\fP [\fIn\fP] The positional parameters from \fIn\fP+1 ... are renamed to .B $1 diff -ruN bash-3.2-patched/doc/bashref.texi bash-3.2-work/doc/bashref.texi --- bash-3.2-patched/doc/bashref.texi 2008-09-10 15:39:53.000000000 +0900 +++ bash-3.2-work/doc/bashref.texi 2008-09-17 20:34:18.000000000 +0900 @@ -2885,6 +2885,13 @@ The return status is non-zero if @code{return} is used outside a function and not during the execution of a script by @code{.} or @code{source}. +@item set0 +@btindex set0 +@example +set0 @var{string} +@end example +Set @code{$0}, the program name. + @item shift @btindex shift @example |
From: Masatake Y. <ya...@re...> - 2008-08-26 02:36:29
|
> Thanks! Should be applied now. Also removed this target in the parent > Makefile which a holdover from the time when we were building builtins > there. > > I had to apply the patch by hand since cut-and pasting into a patch > file didn't work. So please double check. I checed. The patch was applied well. Thank you. Masatake YAMATO |
From: Rocky B. <roc...@gm...> - 2008-08-25 14:12:51
|
Thanks! Should be applied now. Also removed this target in the parent Makefile which a holdover from the time when we were building builtins there. I had to apply the patch by hand since cut-and pasting into a patch file didn't work. So please double check. On Mon, Aug 25, 2008 at 8:29 AM, Masatake YAMATO <ya...@re...> wrote: > Hi, > > The argument for rm in set0$(EXEEXT) target of builtin/Makefile > is wrong. Here is a patch for fixing it. > > 2008-08-25 Masatake YAMATO <ya...@re...> > > * builtin/Makefile.am: Give $@ to rm. > > Index: Makefile.am > =================================================================== > RCS file: /cvsroot/bashdb/bash-3.1/builtin/Makefile.am,v > retrieving revision 1.4 > diff -c -r1.4 Makefile.am > *** Makefile.am 13 Jul 2008 21:20:30 -0000 1.4 > --- Makefile.am 25 Aug 2008 12:26:57 -0000 > *************** > *** 9,15 **** > readarray_LDFLAGS = -shared > > readarray$(EXEEXT): $(readarray_OBJECTS) $(readarray_DEPENDENCIES) > ! @rm -f readarray$(EXEEXT) > $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ \ > $(readarray_LDFLAGS) $(readarray_OBJECTS) $(readarray_LDADD) $(LIBS) > > --- 9,15 ---- > readarray_LDFLAGS = -shared > > readarray$(EXEEXT): $(readarray_OBJECTS) $(readarray_DEPENDENCIES) > ! @rm -f $@ > $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ \ > $(readarray_LDFLAGS) $(readarray_OBJECTS) $(readarray_LDADD) $(LIBS) > > *************** > *** 19,25 **** > set0_builtin = set0 > > set0$(EXEEXT): $(set0_OBJECTS) $(set0_DEPENDENCIES) > ! @rm -f readarray$(EXEEXT) > $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ \ > $(set0_LDFLAGS) $(set0_OBJECTS) $(set0_LDADD) $(LIBS) > > --- 19,25 ---- > set0_builtin = set0 > > set0$(EXEEXT): $(set0_OBJECTS) $(set0_DEPENDENCIES) > ! @rm -f $@ > $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ \ > $(set0_LDFLAGS) $(set0_OBJECTS) $(set0_LDADD) $(LIBS) > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Bashdb-devel mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-devel > |
From: Masatake Y. <ya...@re...> - 2008-08-25 12:29:47
|
Hi, The argument for rm in set0$(EXEEXT) target of builtin/Makefile is wrong. Here is a patch for fixing it. 2008-08-25 Masatake YAMATO <ya...@re...> * builtin/Makefile.am: Give $@ to rm. Index: Makefile.am =================================================================== RCS file: /cvsroot/bashdb/bash-3.1/builtin/Makefile.am,v retrieving revision 1.4 diff -c -r1.4 Makefile.am *** Makefile.am 13 Jul 2008 21:20:30 -0000 1.4 --- Makefile.am 25 Aug 2008 12:26:57 -0000 *************** *** 9,15 **** readarray_LDFLAGS = -shared readarray$(EXEEXT): $(readarray_OBJECTS) $(readarray_DEPENDENCIES) ! @rm -f readarray$(EXEEXT) $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ \ $(readarray_LDFLAGS) $(readarray_OBJECTS) $(readarray_LDADD) $(LIBS) --- 9,15 ---- readarray_LDFLAGS = -shared readarray$(EXEEXT): $(readarray_OBJECTS) $(readarray_DEPENDENCIES) ! @rm -f $@ $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ \ $(readarray_LDFLAGS) $(readarray_OBJECTS) $(readarray_LDADD) $(LIBS) *************** *** 19,25 **** set0_builtin = set0 set0$(EXEEXT): $(set0_OBJECTS) $(set0_DEPENDENCIES) ! @rm -f readarray$(EXEEXT) $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ \ $(set0_LDFLAGS) $(set0_OBJECTS) $(set0_LDADD) $(LIBS) --- 19,25 ---- set0_builtin = set0 set0$(EXEEXT): $(set0_OBJECTS) $(set0_DEPENDENCIES) ! @rm -f $@ $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ \ $(set0_LDFLAGS) $(set0_OBJECTS) $(set0_LDADD) $(LIBS) |
From: Masatake Y. <ya...@re...> - 2008-08-13 10:25:16
|
> Copyright added. Sure, getting into bash is probably a good thing to > do. I thought somewhere I saw a builtin function called something like > SETVAR0 for zsh which does the same thing. I don't see it now though. > But the idea is that if there are other corresponding builtin > functions for other shells, I'd like to try to call this the same > thing and have it work the same way. > > Which reminds me about readarray. zsh does have a builtin function > called mapfile. However that doesn't work like readarray. Instead it > reads a file in as a string preserving and newlines are inside the > string. You'd still have to split the string into an array. > > The purpose of set0 in the debugger is that users often write programs > that refer to $0. For example to display a usage string or maybe they > change the behavior based on how they were called. So this helps in > making these programs act the same way and gives an alternative to > invoking with "bash --debugger". Thank you for the explanation. I think set0 is very good name. The name tell its function well. So I'll push set0 to the bash maintainer. However, I think extending the original `set' command to handle $0 is not so bad. So I'll propose both the name set0 and extending set to the maintainer, and I'll get the comment from him. Masatake YAMATO |
From: Rocky B. <roc...@gm...> - 2008-08-05 11:41:21
|
Copyright added. Sure, getting into bash is probably a good thing to do. I thought somewhere I saw a builtin function called something like SETVAR0 for zsh which does the same thing. I don't see it now though. But the idea is that if there are other corresponding builtin functions for other shells, I'd like to try to call this the same thing and have it work the same way. Which reminds me about readarray. zsh does have a builtin function called mapfile. However that doesn't work like readarray. Instead it reads a file in as a string preserving and newlines are inside the string. You'd still have to split the string into an array. The purpose of set0 in the debugger is that users often write programs that refer to $0. For example to display a usage string or maybe they change the behavior based on how they were called. So this helps in making these programs act the same way and gives an alternative to invoking with "bash --debugger". On Tue, Aug 5, 2008 at 1:11 AM, Masatake YAMATO <ya...@re...> wrote: >> As usual, you are correct. I've also updated the unit test in >> test/unit/test-set0.sh.in so it would have caught at least one of the >> flaws. > > Should I push set0 to Chet Ramey? > If yes please put copyright notice to set0.c. > > Masatake YAMATO > |
From: Masatake Y. <ya...@re...> - 2008-08-05 05:11:44
|
> As usual, you are correct. I've also updated the unit test in > test/unit/test-set0.sh.in so it would have caught at least one of the > flaws. Should I push set0 to Chet Ramey? If yes please put copyright notice to set0.c. Masatake YAMATO |
From: Rocky B. <roc...@gm...> - 2008-08-04 12:32:23
|
Just so there is no surprise. bashdb is undergoing a number of changes I hope to make it better. There are also a few new features. As a result, it's possible I'll mess up and CVS may be unstable. But if you find that to be the case, let me know and I'll try to correct. A couple of months back a book publisher asked me to write a book about bash. Alas, although would really like a good one written at the caliber of say the Pickaxe or Matz/Flannagan/Why book, this is probably a little bit of stretch for me. In fact, there's only one serious bash program I've ever written and as I look at it now there is much that could be improved. After consulting with colleagues, it seems that what's also needed is a book on POSIX shell and something treating that as a programming language and trying to put in in relation to other programming languages. I've found that many of my colleagues really don't understand why here this has to be done and there it works slightly different, but have instead memorized a number of incantations that (sometimes through painful experience) seems to work. If anyone is interested in looking at bits I have right now the contact me. The shells, that attempt POSIX compatibility that I know of are (in alphabetic order) are ash, bash, dash, ksh, and zsh. Right now what I should be writing on is specifically the program development part. But in order to do this I should understand what I'm writing about. Recently I've started work on both ksh and zsh debuggers. Probably the ksh debugger will get done after zsh, unless that get's snagged. My current thought is not to put this in sourceforge under bashdb and CVS but maybe to switch to git somewhere else, perhaps github. |
From: Rocky B. <roc...@gm...> - 2008-08-04 12:14:30
|
Thanks. It is great to have someone else looking over the code. As usual, you are correct. I've also updated the unit test in test/unit/test-set0.sh.in so it would have caught at least one of the flaws. On Mon, Aug 4, 2008 at 7:34 AM, Masatake YAMATO <ya...@re...> wrote: > Hi, > > (I lost je...@gy.... > Please use ya...@re... to contact with me about FOSS.) > > I have a chance to read set0. > I have not had time to build it. However, I could find some lines > which will cause troubles. Could you review following patch? > > > 2008-08-04 Masatake YAMATO <ya...@re...> > > * builtin/set0.c: Fix comments. > (set0_builtin): Free $0 before overwriting. > Return SUCCESS instead of FAILURE. > > Index: set0.c > =================================================================== > RCS file: /cvsroot/bashdb/bash-3.1/builtin/set0.c,v > retrieving revision 1.1 > diff -c -r1.1 set0.c > *** set0.c 23 May 2008 23:55:25 -0000 1.1 > --- set0.c 4 Aug 2008 11:30:01 -0000 > *************** > *** 1,5 **** > /* > ! Extends bash with a builtin function to test if a name is defined or not. > > To install after compiling: > cd *this directory* > --- 1,5 ---- > /* > ! Set $0. > > To install after compiling: > cd *this directory* > *************** > *** 31,38 **** > return (EX_USAGE); > } > > dollar_vars[0] = savestring(list->word->word); > ! return EXECUTION_FAILURE; > } > > struct builtin set0_struct = { > --- 31,41 ---- > return (EX_USAGE); > } > > + if (dollar_vars[0]) > + free (dollar_vars[0]); > + > dollar_vars[0] = savestring(list->word->word); > ! return EXECUTION_SUCCESS; > } > > struct builtin set0_struct = { > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Bashdb-devel mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-devel > |
From: Masatake Y. <ya...@re...> - 2008-08-04 11:34:38
|
Hi, (I lost je...@gy.... Please use ya...@re... to contact with me about FOSS.) I have a chance to read set0. I have not had time to build it. However, I could find some lines which will cause troubles. Could you review following patch? 2008-08-04 Masatake YAMATO <ya...@re...> * builtin/set0.c: Fix comments. (set0_builtin): Free $0 before overwriting. Return SUCCESS instead of FAILURE. Index: set0.c =================================================================== RCS file: /cvsroot/bashdb/bash-3.1/builtin/set0.c,v retrieving revision 1.1 diff -c -r1.1 set0.c *** set0.c 23 May 2008 23:55:25 -0000 1.1 --- set0.c 4 Aug 2008 11:30:01 -0000 *************** *** 1,5 **** /* ! Extends bash with a builtin function to test if a name is defined or not. To install after compiling: cd *this directory* --- 1,5 ---- /* ! Set $0. To install after compiling: cd *this directory* *************** *** 31,38 **** return (EX_USAGE); } dollar_vars[0] = savestring(list->word->word); ! return EXECUTION_FAILURE; } struct builtin set0_struct = { --- 31,41 ---- return (EX_USAGE); } + if (dollar_vars[0]) + free (dollar_vars[0]); + dollar_vars[0] = savestring(list->word->word); ! return EXECUTION_SUCCESS; } struct builtin set0_struct = { |
From: Rocky B. <ro...@pa...> - 2008-07-22 09:03:42
|
You are using bash 3.1-0.06 which is over 2 years old and 3 releases behind. Use 3.1-0.09 and I don't think you will have this problem. There were recent changes for fixing set -u with bashdb-trace (which you are not using here). So even better is to use what is in CVS. On Mon, Jul 21, 2008 at 10:36 PM, Peng Yu <pen...@gm...> wrote: > Hi, > > I have used 'set -u' in my bash script. But it seems that bashdb is > not friendly with 'set -u'. Can somebody fix this in future versions > of bashdb? > > Thanks, > Peng > > > > $ cat echo.sh > #!/bin/bash > > set -u > > echo Hello > > $ bashdb echo.sh > Bourne-Again Shell Debugger, release bash-3.1-0.06 > Copyright 2002, 2003, 2004, 2006 Rocky Bernstein > This is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > > (/tmp/echo.sh:3): > 3: set -u > bashdb<0> n > /usr/share/bashdb/dbg-fns.inc: line 63: _Dbg_file_cmd_StmpSechoDsh: > unbound variable > /usr/share/bashdb/dbg-fns.inc: line 96: _Dbg_action_StmpSechoDsh[5]: > unbound variable > /usr/share/bashdb/dbg-fns.inc: line 96: _Dbg_brkpt_StmpSechoDsh[5]: > unbound variable > (/tmp/echo.sh:5): > 5: echo Hello > bashdb<1> n > Hello > /usr/share/bashdb/dbg-fns.inc: line 63: _Dbg_file_cmd_SusrSbinSbashdb: > unbound variable > /usr/share/bashdb/dbg-fns.inc: line 96: > _Dbg_action_SusrSbinSbashdb[285]: unbound variable > /usr/share/bashdb/dbg-fns.inc: line 96: > _Dbg_brkpt_SusrSbinSbashdb[285]: unbound variable > /usr/share/bashdb/dbg-fns.inc: line 63: _Dbg_read_SusrSbinSbashdb: > unbound variable > /usr/share/bashdb/dbg-fns.inc: line 63: _Dbg_file_cmd_SusrSbinSbashdb: > unbound variable > /usr/share/bashdb/dbg-fns.inc: line 96: > _Dbg_source_SusrSbinSbashdb[285]: unbound variable > (/usr/bin/bashdb:285): > 285: > bashdb<2> q > /usr/share/bashdb/dbg-sig.inc: line 271: BASHDB_RESTART_COMMAND: > unbound variable > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Bashdb-devel mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-devel > |
From: Peng Y. <pen...@gm...> - 2008-07-22 02:35:56
|
Hi, I have used 'set -u' in my bash script. But it seems that bashdb is not friendly with 'set -u'. Can somebody fix this in future versions of bashdb? Thanks, Peng $ cat echo.sh #!/bin/bash set -u echo Hello $ bashdb echo.sh Bourne-Again Shell Debugger, release bash-3.1-0.06 Copyright 2002, 2003, 2004, 2006 Rocky Bernstein This is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. (/tmp/echo.sh:3): 3: set -u bashdb<0> n /usr/share/bashdb/dbg-fns.inc: line 63: _Dbg_file_cmd_StmpSechoDsh: unbound variable /usr/share/bashdb/dbg-fns.inc: line 96: _Dbg_action_StmpSechoDsh[5]: unbound variable /usr/share/bashdb/dbg-fns.inc: line 96: _Dbg_brkpt_StmpSechoDsh[5]: unbound variable (/tmp/echo.sh:5): 5: echo Hello bashdb<1> n Hello /usr/share/bashdb/dbg-fns.inc: line 63: _Dbg_file_cmd_SusrSbinSbashdb: unbound variable /usr/share/bashdb/dbg-fns.inc: line 96: _Dbg_action_SusrSbinSbashdb[285]: unbound variable /usr/share/bashdb/dbg-fns.inc: line 96: _Dbg_brkpt_SusrSbinSbashdb[285]: unbound variable /usr/share/bashdb/dbg-fns.inc: line 63: _Dbg_read_SusrSbinSbashdb: unbound variable /usr/share/bashdb/dbg-fns.inc: line 63: _Dbg_file_cmd_SusrSbinSbashdb: unbound variable /usr/share/bashdb/dbg-fns.inc: line 96: _Dbg_source_SusrSbinSbashdb[285]: unbound variable (/usr/bin/bashdb:285): 285: bashdb<2> q /usr/share/bashdb/dbg-sig.inc: line 271: BASHDB_RESTART_COMMAND: unbound variable |
From: R. B. <ro...@pa...> - 2007-12-11 12:14:43
|
Anders Lindgren and I (but mostly Anders) has been revamping debugging support via GNU Emacs along the lines of the newer gdb debugging in Emacs 22 (gdb-ui.el). For each debug session there are several internal buffers which are constantly updated and contain information about the current state. For example a buffer contains stack information, another the breakpoint information, another display expressions, and so on. These are called "secondary buffers". Because screen real-estate is limited, some of these buffers may be visable in a frame and some not. There are commands to switch to these buffers moving to the visible frame if the buffer is visable, or replacing the secondary buffer that the command was issued from with the desired secondary buffer. The question has come up regarding key bindings and this is where I'd like to solicit comments. In various IDE's like Eclipse, netbeans or Visual Studio, the function key (e.g F5) issue debugger commands. There can be variable to indicate which flavor of keybindings one wants. Some secondary buffers may have specific commands applicable. Right now however there are very few of these, and many of these could be construed applicable even if you aren't in that buffer. For example, one might want frame-moving commands like "up" to be conveniently available even outside the stack buffer. One proposal is to have the capital letter move between secondary buffers as mentioned above (jump to if visible or replace a secondary if not). SPACE step (edebug compatible) < up (Gud uses this and Emacs uses M-< for beginning of buffer) > down (Gud uses this and Emacs uses M-> for beginning of buffer) ? help B goto/display breakpoints buffer C goto/display command buffer D goto/display display O goto/display program output S goto/display source window T goto/display stack-buffer (Perl uses T for stack trace) V goto/display variables buffer b set breakpoint (edebug compatible) c continue (edebug compatible) d remove break f finish n next (edebug compatible) p print q quit (edebug compatible) r restart s step u unset breakpoint (edebug compatible) x temporary breakpoint (edebug compatible) Buffer specific commands Stack buffer return: set frame at this position variables buffer return: edit the variable's value breakpoints: return toggle breakpoint (enable/disable it) |
From: Masatake Y. <je...@gy...> - 2007-11-20 15:25:32
|
> Thanks for the comments. Yes, your message in fact was classified as > "trash". So thanks for not letting this slip and posting. We learn generally we should use this list. |
From: R. B. <ro...@pa...> - 2007-11-17 15:27:37
|
What things do people find most helpful in debugging from emacs? What things in general are lacking? (Of course, I'm mostly interested in the languages cited above and improving debugging interaction with those, but other information could be helpful as well.) One thing I notice regarding edebug which seems different than gud debugging is that it sets up (I guess) a recursive edit on the program begin debugged so that it can bind keys to debug functions like step, next, and so on. Do people generally find it useful when debugging to set the program read only so that it can't be modified while debugging? Or is this an annoyance? For Emacs Lisp code, I find C-x C-e helpful and use that a lot. For these other programming languages that could be bound to eval using the debugger. (And if not debugging, it might fall back to running the expression in a comint shell buffer). |
From: Rocky B. <roc...@gm...> - 2007-11-16 16:12:30
|
Thanks for the comments. Yes, your message in fact was classified as "trash". So thanks for not letting this slip and posting. On Nov 16, 2007 12:23 AM, Masatake YAMATO <je...@gy...> wrote: > (I've sent this mail privately to Rocky. However, I'm afraid > that my mail is dropped by spam filter. So I'll send this here.) > > I've read new bashdb.el code briefly. > Changes are much larger than I thought, so I give up detailed > review. I'll read deeply after bash4 is released. > > > Random some comments: > > > > ;;----------------------------------------------------------------------------- > > ;; ALB - redefinition of gud-reset for our own purposes > > > (defvar bashdb--orig-gud-reset (symbol-function 'gud-reset)) > > > (defun gud-reset () > > "Redefinition of `gud-reset' to take care of bashdb cleanup." > > (funcall bashdb--orig-gud-reset) > > (dolist (buffer (buffer-list)) > > (when (string-match "\\*bashdb-[a-z]+\\*" (buffer-name buffer)) > > (let ((w (get-buffer-window buffer))) > > (when w (delete-window w))) > > (kill-buffer buffer)))) > > > You should use defadvice. See advice.el if this is the first time > you hear defadvice. With defadvice the code can be rewritten like > this: > > (defadvice gud-reset (after bashdb-kill-buffer-and-window activate) > "Cleanup bashdb related buffers and windows." > > ;; See how gdb-reset is called in gud.el::gud-sentinel. > (when (or (memq gud-minor-mode-type '(bashdb)) > (memq (buffer-local-value 'gud-minor-mode > gud-comint-buffer) > '(bashdb))) > (bashdb-reset))) > > (defun bashdb-reset () > (dolist (buffer (buffer-list)) > (when (string-match "\\*bashdb-[a-z]+\\*" (buffer-name buffer)) > (let ((w (get-buffer-window buffer))) > (when w (delete-window w))) > (kill-buffer buffer)))) > > I think bashdb-bashdbtrack-* should be moved to bashdb-track.el. > (Further more I think bashdb-track.el could be splited into > comint-track.el(or comint-trace.el) > and bashdh-track.el.) > > > > (or (assq 'bashdb-bashdbtrack-is-tracking-p minor-mode-alist) > > (push '(bashdb-bashdbtrack-is-tracking-p > > bashdb-bashdbtrack-minor-mode-string) > > minor-mode-alist)) > > On GNU Emacs, `define-minor-mode' is available. > > Masatake YAMATO > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Bashdb-devel mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-devel > |
From: Masatake Y. <je...@gy...> - 2007-11-16 05:23:25
|
(I've sent this mail privately to Rocky. However, I'm afraid that my mail is dropped by spam filter. So I'll send this here.) I've read new bashdb.el code briefly. Changes are much larger than I thought, so I give up detailed review. I'll read deeply after bash4 is released. Random some comments: > ;;----------------------------------------------------------------------------- > ;; ALB - redefinition of gud-reset for our own purposes > (defvar bashdb--orig-gud-reset (symbol-function 'gud-reset)) > (defun gud-reset () > "Redefinition of `gud-reset' to take care of bashdb cleanup." > (funcall bashdb--orig-gud-reset) > (dolist (buffer (buffer-list)) > (when (string-match "\\*bashdb-[a-z]+\\*" (buffer-name buffer)) > (let ((w (get-buffer-window buffer))) > (when w (delete-window w))) > (kill-buffer buffer)))) You should use defadvice. See advice.el if this is the first time you hear defadvice. With defadvice the code can be rewritten like this: (defadvice gud-reset (after bashdb-kill-buffer-and-window activate) "Cleanup bashdb related buffers and windows." ;; See how gdb-reset is called in gud.el::gud-sentinel. (when (or (memq gud-minor-mode-type '(bashdb)) (memq (buffer-local-value 'gud-minor-mode gud-comint-buffer) '(bashdb))) (bashdb-reset))) (defun bashdb-reset () (dolist (buffer (buffer-list)) (when (string-match "\\*bashdb-[a-z]+\\*" (buffer-name buffer)) (let ((w (get-buffer-window buffer))) (when w (delete-window w))) (kill-buffer buffer)))) I think bashdb-bashdbtrack-* should be moved to bashdb-track.el. (Further more I think bashdb-track.el could be splited into comint-track.el(or comint-trace.el) and bashdh-track.el.) > (or (assq 'bashdb-bashdbtrack-is-tracking-p minor-mode-alist) > (push '(bashdb-bashdbtrack-is-tracking-p > bashdb-bashdbtrack-minor-mode-string) > minor-mode-alist)) On GNU Emacs, `define-minor-mode' is available. Masatake YAMATO |
From: R. B. <ro...@pa...> - 2007-10-29 18:41:24
|
I happened to notice a patch by Alberto Griggio for the python debugger pydb, after releasing bashd 3.1-0.09. The patch improves emacs interaction by using gdb's annotation mechanism. The jist is that the debugger spits out breakpoint and stack information whenever this changes in a special section or as an "annotation". Inside Emacs buffers are saved for each section of information. gdb's annotation mechanism isn't restricted to just improving emacs, other front ends can make use of it as well. I've retrofited this pydb change for bashdb and that is in CVS. If you try it out let me know what you think. I'll probably also make a change for ruby-debug as well. |
From: R. B. <ro...@pa...> - 2007-10-14 04:03:51
|
Mostly clear out some old changes, I'm thinking about making another release around October 27th. It iwll be 3.1.0.9 (which works on bash 3.1 and 3.2). Here's what we have listed in NEWS: - Add set/show trace-commands to make the same as gdb 6.6 - show commands now allows for a starting number and +, same as gdb - Reduce assumption that undefined means '' - initialize more variables. (working towards inserting "set -u". - variable and tilde expansion now occurs in cd command. Note gdb does tilde expansion but not variable expansion like $HOME. - add linetrace delay - make FreeBSD tests work, cygwin signals are working so test are run there - documentation updates - emacs code improved - some installation bugs fixed If you can test what's in CVS I'd appreciate it. A candidate tarball is at http://bashdb.sf.net/bashdb-3.1-0.09.tar.gz Thanks. |
From: R. B. <ro...@pa...> - 2007-08-16 11:57:24
|
I recently noticed an installation problem in bashdb which was just fixed in CVS. Debugger files dbg-sig.inc, etc. don't get installed properly (e.g. in say /usr/local/share/bashdb) Actually they do get installed, but they then get removed when a symlink from bashdb-main.inc gets added to dbg-main.inc. I've put in a somewhat horrible hack on top of that existing hack to make sure that if the rm is done we re-install the package files. There's probably a better way. I'm sure folks have mentioned this in the past. In fact I think someone recently mentioned this I think with respect to installing on OSX. And alas I can't find the email, posting or my response (or I'd send that person an update). I recall mentioning using remake to track the problem down. And in fact that's what I just did for myself. (Remake segv'd with a glibc free error but that's another matter.) |
From: Rocky B. <roc...@gm...> - 2007-07-16 02:30:10
|
This message bashdb: cannot read . Perhaps bashdb is installed wrong. means bashdb can't read the directory where it thinks bashdb is (temporarily) installed. The -L option allows one to indicate where this directory is. See around line 209 of the bashdb script. I'll change the wording on this error message to try to be more clear. So in essence all of the tests are failing.. Sometimes this happens when the "build" directory location is set incorrectly. There's lots of autotools configuration magic that's supposed to make that work, but how to use autoconf/automake has always been a great mystery to me. In this regard I generally use the Make Debugger/tracer (remake) that I wrote to help me figure out what's going on, e.g. why the makefile thinks "." is the build directory, etc. On 7/15/07, Louis Munro <lm...@lo...> wrote: > > Rocky Bernstein wrote: > > I don't see enough information on the failure to give anything but > > general suggestions. The most obvious one is to pay attention to > > warnings and messages that appear when you run "configure" "make" and > > of course "make test". > > > > From the output below I see that one of the test programs that failed is > > called run-watch2. It should be located in a directory called "test". > > Run that single program (run-watch2) from the directory it is located > > in. The idea of that test program and others is to run a sequence of > > debuggers commands and compare the output against known good output. > > > > Good luck! > > > > Ok, here are (attached) the complete outputs of ./configure, make and > make check. Hope that helps. > The only thing that sticks out is this in make-check.log: > -bashdb: cannot read . Perhaps bashdb is installed wrong. > -bashdb: or try using -L (with a different directory). > > bashdb isn't installed yet (I haven't run make install because of the > errors) and all files in this directory are readable. > > Thanks for your help [log output deleted] |