Donate Share

VSMap3D

Tracker: Bugs

5 Seg fault when jump pointers not set - ID: 2689798
Last Update: Comment added ( templer666 )

Using vsmap3d -1.3.5 on VegaStrike data from svn revision 12541.

Click on Baja sector, get a seg fault with the following console output:
jonathan@odin:~/bin$ vsmap3d
QString::arg: Argument missing: Warning! destination system pointer of jump
to %s is not set!<br>, reid
QString::arg: Argument missing: Warning! destination system pointer of jump
to %s is not set!<br>, Ellison
QString::arg: Argument missing: Warning! destination system pointer of jump
to %s is not set!<br>, Venture
QString::arg: Argument missing: Warning! destination system pointer of jump
to %s is not set!<br>, Tesla
QString::arg: Argument missing: Warning! destination system pointer of jump
to %s is not set!<br>, Dienno
Segmentation fault

Possibly root cause is errors in VegaStrike data, but perhaps vsmap3d
should be tolerant of such faults


Jonathan R Richards ( jnorichards ) - 2009-03-17 09:08

5

Open

None

Nobody/Anonymous

None

None

Public


Comments ( 2 )




Date: 2009-11-03 21:19
Sender: templer666Project Admin

I'm on it, but this seems to be a tough one. Problem does not seem to be
data related. When universe is loaded and you select other sectors that
don't produce the seg fault and cycle through them randomly it may occor
that a previously "good" sector will cause the seg fault suddenly.


Date: 2009-03-17 21:24
Sender: jnorichards

I've checked the data in the file vsmap3d is parsing, milky_way.xml, and
can find no obvious mistakes in the jump specifications there, so the
probability is that vsmap3d is at fault, not the data.


Log in to comment.

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.