On Fri, Jan 23, 2009 at 04:05:38PM +0100, Andreas Tille wrote:
> I'm probably blind for the problem but this exit status 128 without
> any debug information is quite less. What are the best strategies
> to track down the problematic line of code which causes the problem.
I've not looked at the package at all but adding a -x to the shell
invocation like so:
#!/bin/sh -x
will cause it to print out what it's executing line by line.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
