Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

3.1_rc3 delivery point segfaults, StructIsFactory, intDisplayDPButton, structPlaceDroid #3768

Closed
wzdev-ci opened this issue Oct 30, 2012 · 11 comments
Closed

3.1_rc3 delivery point segfaults, StructIsFactory, intDisplayDPButton, structPlaceDroid #3768

wzdev-ci opened this issue Oct 30, 2012 · 11 comments
Labels
closed component: other normal
Milestone
unspecified

Comments

@wzdev-ci
Copy link
Contributor

keyword_segfault resolution_Needs reevaluating for current version (3.2.3) type_bug | by scrivi@...

During normal game play program exit and segfaults
Since it happens a lot with this release (running on ubuntu 12.04) I'm reporting it including the dump file

Issue migrated from trac:3768 at 2022-04-16 10:41:06 -0700
@wzdev-ci
Copy link
Contributor Author

scrivi@... uploaded file warzone2100.gdmp-Dg8FNo (38.8 KiB)

example dump 1

@wzdev-ci
Copy link
Contributor Author

scrivi@... uploaded file warzone2100.gdmp-Nkc7oV (105.8 KiB)

example dump 2

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Nov 2, 2012

Per changed blocking which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Nov 2, 2012

Per changed blockedby which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Nov 2, 2012

Per commented

Anything special that you do? In both crashes, it happens when a factory produces a droid and wants to place it next to a factory flag.

@wzdev-ci
Copy link
Contributor Author

Cyp changed title from 3.1_rc3 segfaults to 3.1_rc3 delivery point segfaults, StructIsFactory, intDisplayDPButton, structPlaceDroid

@wzdev-ci
Copy link
Contributor Author

Cyp commented

An equivalent dump 2 in #3790.

@wzdev-ci
Copy link
Contributor Author

scrivi@... commented

I don't remember doing anything in particular.
It's weird because since I reported this bug it never happened again. Since then I just changed the available space in /tmp I don't know if this is related at all. I'll report back if it happens again.
thanks

@wzdev-ci
Copy link
Contributor Author

vexed changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

vexed changed resolution from `` to Needs reevaluating for current version (3.1.0)

@wzdev-ci
Copy link
Contributor Author

vexed commented

Need to know if these issues still happen with the release of 3.1.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
closed component: other normal
Projects
None yet
Milestone
unspecified
Development

No branches or pull requests
1 participant
@wzdev-ci