On Wed, 10 Jul 2013 15:37:18 -0400 Alexandre Rebert <[email protected]>
wrote:
> Package: omniorb
> Version: 4.1.6-2
> Severity: normal
> User: [email protected]
> Usertags: mayhem
> 
> omniMapper crashes with exit status 139. We confirmed the crash by
> re-running it in a fresh debian unstable installation.

Apologies for taking so long to reply to this bug. Omniorb 4.2.5 is now
available in Debian unstable, testing and a backport has been made to
stable (bullseye).

The URL in the bug is now a 404 but the omniMapper-report.tar.bz2
attachment remains, so thanks for providing that.

I have reproduced the crash on Stretch (omniorb 4.1.6-2.1+b1).
crash.sh: line 12: warning: command substitution: ignored null byte in
input
crash.sh: line 19:  7401 Segmentation fault      env -i MALLOC_CHECK_=0
$GDB /usr/bin/omniMapper "`cat $DIR/argv_1.symb`" <
"$DIR/file___dev__stdin.symb"


The crash no longer happens with 4.2.5:
crash.sh: line 12: warning: command substitution: ignored null byte in
input

usage: omniMapper [-port <port>]
                  [-config <config file>]
                  [-v]

With no -port argument, the standard default of 2809 is used.

Use -config to specify the location of omniMapper's config file.

Alternatively, set the environment variable OMNIMAPPER_CONFIG
or use the default /etc/omniMapper.cfg.

Use -v to verbosely record what's going on.

I'll close this bug report with the next upload of omniorb.

-- 
Neil Williams
=============
https://linux.codehelp.co.uk/

Attachment: pgp743XM79ry_.pgp
Description: OpenPGP digital signature

Reply via email to