createHierarchy segfault

[samtuke]

$ ./createHierarchy great_britain.osrm preprocessing data from input file great_britain.osrm using STL serial mode Importing n = 8291624 nodes ... and 8732334 edges ...ok initializing contractor ...Edge Weight too large -> May lead to invalid CH Edge Weight too large -> May lead to invalid CH Edge Weight too large -> May lead to invalid CH Edge Weight too large -> May lead to invalid CH Edge Weight too large -> May lead to invalid CH ok removed 15822 edges of 17464658 Contractor is using 2 threads initializing elimination PQ ...ok preprocessing .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100% [contractor] checking sanity of generated data ...ok [contractor] max level: 95 sorting level info writing level info Scanning for useless shortcuts Removing edges Removed 1894 useless shortcuts Serializing edges . 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100% writing node map ...ok [STXXL-MSG] STXXL v1.2.1 (release) [STXXL-ERRMSG] Warning: no config file found. [STXXL-ERRMSG] Using default disk configuration. [STXXL-MSG] 1 disks are allocated, total space: 1000 MB building grid .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100% sorting grid data consisting of 9423259 edges...ok in 16.9068s writing data .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100% finished Segmentation fault (core dumped)

Where is the core dump data saved to for inspection?

[DennisOSRM]

Are you using stxxl 1.2.x? If so, please switch to 1.3.1.

You should be on the safe side ignoring this error, because once
createHierarchy says "finished" it has finished writing all data to
disk. Previous versions of stxxl had a non-serious bug where this
segfault may happen.

Am 09.11.2011 17:21, schrieb Sam Tuke:

$ ./createHierarchy great_britain.osrm preprocessing data from input file great_britain.osrm using STL serial mode Importing n = 8291624 nodes ... and 8732334 edges ...ok initializing contractor ...Edge Weight too large -> May lead to invalid CH Edge Weight too large -> May lead to invalid CH Edge Weight too large -> May lead to invalid CH Edge Weight too large -> May lead to invalid CH Edge Weight too large -> May lead to invalid CH ok removed 15822 edges of 17464658 Contractor is using 2 threads initializing elimination PQ ...ok preprocessing .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100% [contractor] checking sanity of generated data ...ok [contractor] max level: 95 sorting level info writing level info Scanning for useless shortcuts Removing edges Removed 1894 useless shortcuts Serializing edges . 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100% writing node map ...ok [STXXL-MSG] STXXL v1.2.1 (release) [STXXL-ERRMSG] Warning: no config file found. [STXXL-ERRMSG] Using default disk configuration. [STXXL-MSG] 1 disks are allocated, total space: 1000 MB building grid .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100% sorting grid data consisting of 9423259 edges...ok in 16.9068s writing data .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100% finished Segmentation fault (core dumped)

Where is the core dump data saved to for inspection?

---

Reply to this email directly or view it on GitHub:
#24

Karlsruher Institut für Technologie (KIT)
Institut für Theoretische Informatik

Dennis Luxen
Wissenschaftler

Am Fasanengarten 5
Gebäude 50.34, Zimmer 220
76131 Karlsruhe

Telefon: +49 721 608-46781
Fax: +49 721 608-43088
E-Mail: [email protected]

KIT - Universität des Landes Baden-Württemberg und nationales
Großforschungszentrum in der Helmholtz-Gemeinschaft

[samtuke]

Thanks for the feedback.

I am using 1.2. Good to know the error isn't fatal.

no .names file has been generated however; I assumed this was due to the segfault - is this in fact unrelated? routed will not start due to missing .names file.

Sam.

[samtuke]

I have also tried using a .names file from another instance of OSRM on another machine (using the same .osrm map data file however), and get another segfault, this time from routed:

$ ./routed [server] starting up engines, saved at Wed Nov 9 13:03:50 2011 [server] http 1.1 compression handled by zlib version 1.2.5 [objects] loading query data structures ...Segmentation fault (core dumped)

[DennisOSRM]

Not sure why no names files has been generated. Tested twice on
different test sets and it works fine every time.

Thanks for the feedback.

I am using 1.2. Good to know the error isn't fatal.

no .names file has been generated however; I assumed this was due to the segfault - is this in fact unrelated? routed will not start due to missing .names file.

Sam.

---

Reply to this email directly or view it on GitHub:
#24 (comment)

[samtuke]

I refreshed the repository and recompiled, the routed segfault has disappeared, so closing this issue.

[DennisOSRM]

Thanks for the feedback

[kdelchev]

I get 'segmentation fault (core dumped)' error when run osrm-routed and try to viaroute some coordinates. Already extracted and prepared the index files again, pre-compiled the osrm with --build=debug option and get tons of messages like these:

[debug Server/DataStructures/../../DataStructures/StaticGraph.h:108] cannot find second segment of edge (5488,5485,292341544) [debug Server/DataStructures/../../DataStructures/StaticGraph.h:103] cannot find first segment of edge (5492,292341540,292341544) [debug Server/DataStructures/../../DataStructures/StaticGraph.h:108] cannot find second segment of edge (5492,292341540,292341544) [debug Server/DataStructures/../../DataStructures/StaticGraph.h:103] cannot find first segment of edge (5496,290542845,5489) [debug Server/DataStructures/../../DataStructures/StaticGraph.h:108] cannot find second segment of edge (5496,290542845,5489)

After the ./osrm-routed command start showing the messages I can't stop it with Ctrl+C and have to kill the process.

[DennisOSRM]

Looks like broken data and/or inconsistent binaries.