osirisgothra · October 5, 2014 20:15 · osirisgothra · Oct 5, 2014
diff --git a/Longer Question About ddd, bashdb, and bash b/Longer Question About ddd, bashdb, and bash
 According to [this snapshot][1] they do, but how they do is beyond me. I have tried building all the suggested versions from SO, of course I used the first ones that came with Ubuntu 13.10 LTS, and then read that I should use different ones (you can find out, there is not much about this on google or SO, and what there is seems to not work at least for me). 

 Is there anyone out there that has actually had bashdb and DDD working together as that screenshot suggests? I have been able to get it to 'not' show that 'Bash could not be started' dialog, which you get if you try to do it the 'right way' by specifying the --debugger, however, it then just freezes up, doesn't load the source file, and endlessly says 'opening session xxxx..' OR it crashes telling me I found a bug in DDD.

 It's hard to think that this is the fault of DDD because EVERY other debugger works perfect for me in DDD, just not bashdb. And I have tried MANY different builds (versions is more like it since there is no compiling really) of bashdb. On the last one AND the one I got from the repository, I had to REWRITE some of bashdb's code just to get the 'step+' and 'step-' commands to even work. 

  BashDB seems to be pretty buggy and It is very fragile whenever I use it to debug scripts that I know are not bugged (I have even used it on scripts from the ubuntu repos, ones like the bash_completion that are tried and true) For example, the watche [not watch] command. 

 So.. my question again is, is there ANYONE that has successfully got this to work like the snapshot shows AND can tell me what the secret to doing it is... am I just incredibly stupid or is there really some bad thing going on with bashdb?

 PS: Though I have had doubts about DDD being the culprit, I, by the advice of others HAVE tried to build and compile the 'said-to-be-working-with-bashdb-versions' of DDD, it runs just about the same in all situations, and I am pretty decent about building and installing. (where files are supposed to go, what prefixes are, where libraries belong, etc) so I have not run into any issues making either bashdb or DDD separately. However, if this persists, I might just write my own debugger.


  [1]: http://bashdb.sourceforge.net/
	According to [this snapshot][1] they do, but how they do is beyond me. I have tried building all the suggested versions from SO, of course I used the first ones that came with Ubuntu 13.10 LTS, and then read that I should use different ones (you can find out, there is not much about this on google or SO, and what there is seems to not work at least for me).

	Is there anyone out there that has actually had bashdb and DDD working together as that screenshot suggests? I have been able to get it to 'not' show that 'Bash could not be started' dialog, which you get if you try to do it the 'right way' by specifying the --debugger, however, it then just freezes up, doesn't load the source file, and endlessly says 'opening session xxxx..' OR it crashes telling me I found a bug in DDD.

	It's hard to think that this is the fault of DDD because EVERY other debugger works perfect for me in DDD, just not bashdb. And I have tried MANY different builds (versions is more like it since there is no compiling really) of bashdb. On the last one AND the one I got from the repository, I had to REWRITE some of bashdb's code just to get the 'step+' and 'step-' commands to even work.

	BashDB seems to be pretty buggy and It is very fragile whenever I use it to debug scripts that I know are not bugged (I have even used it on scripts from the ubuntu repos, ones like the bash_completion that are tried and true) For example, the watche [not watch] command.

	So.. my question again is, is there ANYONE that has successfully got this to work like the snapshot shows AND can tell me what the secret to doing it is... am I just incredibly stupid or is there really some bad thing going on with bashdb?

	PS: Though I have had doubts about DDD being the culprit, I, by the advice of others HAVE tried to build and compile the 'said-to-be-working-with-bashdb-versions' of DDD, it runs just about the same in all situations, and I am pretty decent about building and installing. (where files are supposed to go, what prefixes are, where libraries belong, etc) so I have not run into any issues making either bashdb or DDD separately. However, if this persists, I might just write my own debugger.


	[1]: http://bashdb.sourceforge.net/