Error message does not say much (and how to enable stack trace?)

A recent run of our gulp-compass task failed on our CentOS build server:

```
{ [Error: Compass failed]
message: 'Compass failed',
fileName: '/home/buildagent/workspace/xxx/assets/theming/yyy.scss',
showStack: false,
showProperties: true,
plugin: 'gulp-compass',
__safety: { toString: [Function] } }
```

It doesn't say much, why, what and where the error is coming from. How can we set showStack to true?

We are using gulp-compass v2.0.3 here and on the build server we have these gems installed:

```
compass (1.0.1, 0.12.1)
compass-core (1.0.1)
compass-import-once (1.0.5)
```

our gulp task is:

``` coffee
gulp.task('theming', ['theming:static'], ->
gulp.src("assets/theming/**/brands/#{config.brand}/*.scss")
.pipe(compass(
debug: config.debug
logging: config.debug
comments: not config.sass.compress
sourcemap: config.sass.sourcemaps
style: config.sass.style
sass: 'assets/theming/brands'
css: "#{paths.public}/brands"
image: "#{paths.public}/images"
font: "#{paths.public}/fonts"
import_path: path.resolve('assets/theming')
config_file: compassConfig(
"""
generated_images_dir = "#{paths.public}/images"
asset_cache_buster { "v=#{version}" }
"""
)
))
.on('error', console.error.bind(console))
.pipe(tap(logFile))
)
```

any clues?

Start with the shown Gulp task and its .on('error', console.error.bind(console)) handler, then inspect gulp-compass v2.0.3's error reporting on a CentOS build using the listed Compass gems. Reproduce the failed Compass task and determine whether the stack trace can be enabled or whether the error output needs to expose more context; done means the failure identifies its cause and location clearly.

Written by the indexing model from the issue text.