• denizzzka (79/79) Feb 23 2016 Hi!
• Vladimir Panteleev (3/8) Feb 23 2016 Shells process signal exit codes in a special way. Try

denizzzka <den den.com> writes:

Hi!

I have a code with segfault. I decided to try to take advantage 
with dub dustmite:

$ dub dustmite ~/ssd/pgator_dustmite0 --program-status=139 -- 
--config=my_pgator.conf --debug=true
WARNING: A deprecated branch based version specification is used 
for the dependency vibe-d-postgresql. Please use numbered 
versions instead. Also note that you can still use the 
dub.selections.json file to override a certain dependency to use 
a branch instead.
Copy package 'pgator' to destination folder...
Copy package 'vibe-d-postgresql' to destination folder...
Copy package 'dpq2' to destination folder...
Copy package 'derelict-pq' to destination folder...
Copy package 'derelict-util' to destination folder...
Copy package 'vibe-d' to destination folder...
Copy package 'libasync' to destination folder...
Copy package 'memutils' to destination folder...
Copy package 'libev' to destination folder...
Copy package 'libevent' to destination folder...
Copy package 'openssl' to destination folder...
Executing dustmite...
None => No
object.Exception DustMite/dustmite.d(243): Initial test fails

but if I try to run already compiled binary it is successfully 
core dumps:

$ ./pgator --config=my_pgator.conf --debug=true; echo $?
2016-02-23T18:07:00.748:package.d:_sharedStaticCtor6:9 DerelictPQ 
loading...
2016-02-23T18:07:00.748:package.d:_sharedStaticCtor6:16 
...DerelictPQ loading finished
2016-02-23T18:07:00.750:package.d:connectionFactory:50 creating 
new connection
2016-02-23T18:07:00.750:package.d:connectionFactory:54 new 
connection is started
2016-02-23T18:07:00.750:package.d:runStatementBlockingManner:126 
runStatementBlockingManner
2016-02-23T18:07:00.750:package.d:doQuery:66 get connection from 
a pool
2016-02-23T18:07:00.753:package.d:doQuery:90 doesQuery() call
2016-02-23T18:07:00.753:package.d:__lambda5:140 consumeInput()
2016-02-23T18:07:00.753:package.d:__lambda5:145 getResult()
2016-02-23T18:07:00.753:package.d:__lambda5:145 getResult()
2016-02-23T18:07:00.754:app.d:main:88 found method row: 
"echo"	"SELECT $1::text as echoed"	["value_for_echo"]	false	
2016-02-23T18:07:00.754:app.d:main:137 Method echo loaded. 
Content: Method("echo", "SELECT $1::text as echoed", 
["value_for_echo"], false)
2016-02-23T18:07:00.754:app.d:main:88 found method row: 
"echo2"	"SELECT $1::text"	["value_for_echo"]	NULL	
2016-02-23T18:07:00.754:app.d:main:132 Value of column 
one_row_flag is NULL, skipping reading of method echo2
2016-02-23T18:07:00.754:app.d:main:88 found method row: 
"wrong_sql_statement"	"wrong SQL statement"	[]	false	
2016-02-23T18:07:00.754:app.d:main:137 Method wrong_sql_statement 
loaded. Content: Method("wrong_sql_statement", "wrong SQL 
statement", [], false)
2016-02-23T18:07:00.754:app.d:main:141 Number of methods in the 
table "pgator_rpc": 3, failed to load: 1
2016-02-23T18:07:00.754:app.d:__foreachbody18:148 try to prepare 
method wrong_sql_statement
2016-02-23T18:07:00.754:package.d:runStatementBlockingManner:126 
runStatementBlockingManner
2016-02-23T18:07:00.754:package.d:doQuery:66 get connection from 
a pool
2016-02-23T18:07:00.754:package.d:doQuery:90 doesQuery() call
2016-02-23T18:07:00.754:package.d:__lambda5:140 consumeInput()
2016-02-23T18:07:00.754:package.d:__lambda5:145 getResult()
2016-02-23T18:07:00.754:package.d:__lambda5:145 getResult()
2016-02-23T18:07:00.755:app.d:__foreachbody18:160 ОШИБКА:  ошибка 
синтаксиса (примерное положение: "wrong")
LINE 1: wrong SQL statement
         ^
, skipping preparing of method wrong_sql_statement
2016-02-23T18:07:00.755:app.d:__foreachbody18:162 catched
2016-02-23T18:07:00.755:app.d:__foreachbody18:165 next
Ошибка сегментирования (core dumped)
139

How how to understand why dub dustmite doesn't work for me?

Vladimir Panteleev <thecybershadow.lists gmail.com> writes:

On Tuesday, 23 February 2016 at 11:09:00 UTC, denizzzka wrote:
 Hi!

 I have a code with segfault. I decided to try to take advantage 
 with dub dustmite:

 $ dub dustmite ~/ssd/pgator_dustmite0 --program-status=139 -- 
 --config=my_pgator.conf --debug=true

Shells process signal exit codes in a special way. Try 
`--program-status=-11`.