yade-multi segfault
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Yade |
New
|
Undecided
|
Unassigned |
Bug Description
I have segmentation fault with yade-multi for rev2418:
* "Ошибка сегментирования" below translates as "Segmentation fault"
sega@think:
Will run `/home/
Will use table `multi.table', with available lines 2, 3, 4, 5, 6, 7.
Will use lines 2 (reference), 3 (hi_v), 4 (lo_v), 5 (hi_rho), 6 (hi_rho_v), 7 (hi_rh0_lo_v).
Master process pid 6315
Job summary:
#0 (reference/2): PARAM_TABLE=
#1 (hi_v/2): PARAM_TABLE=
#2 (lo_v/2): PARAM_TABLE=
#3 (hi_rho/2): PARAM_TABLE=
#4 (hi_rho_v/2): PARAM_TABLE=
#5 (hi_rh0_lo_v/2): PARAM_TABLE=
http://
#0 (reference/2) started on Sun Aug 29 22:19:32 2010
sh: line 1: 6319 Ошибка сегментирования PARAM_TABLE=
#0 (reference/2) FAILED (exit status 35584), duration 00:00:09, log multi.reference.log
#1 (hi_v/2) started on Sun Aug 29 22:19:42 2010
sh: line 1: 6357 Ошибка сегментирования PARAM_TABLE=
#1 (hi_v/2) FAILED (exit status 35584), duration 00:00:01, log multi.hi_v.log
#2 (lo_v/2) started on Sun Aug 29 22:19:44 2010
sh: line 1: 6392 Ошибка сегментирования PARAM_TABLE=
#2 (lo_v/2) FAILED (exit status 35584), duration 00:00:01, log multi.lo_v.log
#3 (hi_rho/2) started on Sun Aug 29 22:19:45 2010
sh: line 1: 6397 Ошибка сегментирования PARAM_TABLE=
#3 (hi_rho/2) FAILED (exit status 35584), duration 00:00:01, log multi.hi_rho.log
#4 (hi_rho_v/2) started on Sun Aug 29 22:19:47 2010
sh: line 1: 6402 Ошибка сегментирования PARAM_TABLE=
#4 (hi_rho_v/2) FAILED (exit status 35584), duration 00:00:01, log multi.hi_rho_v.log
#5 (hi_rh0_lo_v/2) started on Sun Aug 29 22:19:49 2010
sh: line 1: 6407 Ошибка сегментирования PARAM_TABLE=
#5 (hi_rh0_lo_v/2) FAILED (exit status 35584), duration 00:00:01, log multi.hi_
All jobs finished, total time 00:00:17
Log files:
multi.reference.log multi.hi_v.log multi.lo_v.log multi.hi_rho.log multi.hi_rho_v.log multi.hi_
Bye.
Ошибка сегментирования
I do not have the dbg-compiled version now, but after I get it, I will send more data... (if need)...
Marked duplicate, it is (very likely) a known issue with log4cxx covered by the other bug.