{"action":"created","issue":{"url":"https://api.github.com/repos/osmcode/osmium-tool/issues/36","repository_url":"https://api.github.com/repos/osmcode/osmium-tool","labels_url":"https://api.github.com/repos/osmcode/osmium-tool/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/osmcode/osmium-tool/issues/36/comments","events_url":"https://api.github.com/repos/osmcode/osmium-tool/issues/36/events","html_url":"https://github.com/osmcode/osmium-tool/issues/36","id":177384361,"number":36,"title":"check-apply-changes-mixed{1,2} tests segfault on mips & mipsel","user":{"login":"sebastic","id":4605306,"avatar_url":"https://avatars0.githubusercontent.com/u/4605306?v=3","gravatar_id":"","url":"https://api.github.com/users/sebastic","html_url":"https://github.com/sebastic","followers_url":"https://api.github.com/users/sebastic/followers","following_url":"https://api.github.com/users/sebastic/following{/other_user}","gists_url":"https://api.github.com/users/sebastic/gists{/gist_id}","starred_url":"https://api.github.com/users/sebastic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sebastic/subscriptions","organizations_url":"https://api.github.com/users/sebastic/orgs","repos_url":"https://api.github.com/users/sebastic/repos","events_url":"https://api.github.com/users/sebastic/events{/privacy}","received_events_url":"https://api.github.com/users/sebastic/received_events","type":"User","site_admin":false},"labels":[{"id":67977248,"url":"https://api.github.com/repos/osmcode/osmium-tool/labels/bug","name":"bug","color":"fc2929","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-09-16T09:46:04Z","updated_at":"2017-03-08T07:58:26Z","closed_at":null,"body":"The `check-apply-changes-mixed1` & `check-apply-changes-mixed2` caused the osmium-tool 1.4.0 builds on mips & mipsel to fail due to segfaults in these tests:\n\n```\n        Start  20: check-apply-changes-mixed1\n 19/198 Test  #20: check-apply-changes-mixed1 ................***Exception: SegFault  0.10 sec\n\n        Start  21: check-apply-changes-mixed2\n 21/198 Test  #21: check-apply-changes-mixed2 ................***Exception: SegFault  0.10 sec\n[...]\n99% tests passed, 2 tests failed out of 198\n\nTotal Test time (real) =  29.51 sec\n\nThe following tests FAILED:\n     20 - check-apply-changes-mixed1 (SEGFAULT)\n     21 - check-apply-changes-mixed2 (SEGFAULT)\nErrors while running CTest\n```\n\nFull buildlogs: [mips](https://buildd.debian.org/status/fetch.php?pkg=osmium-tool&arch=mips&ver=1.4.0-1&stamp=1473985894), [mipsel](https://buildd.debian.org/status/fetch.php?pkg=osmium-tool&arch=mipsel&ver=1.4.0-1&stamp=1473985550)\n\nI've run the tests manually on the mips porterbox under gdb.\n\ncheck-apply-changes-mixed1:\n\n```\n(gdb) run\nStarting program: /home/sebastic/git/pkg-grass/osmium-tool-1.4.0/obj-mips-linux-gnu/src/osmium apply-changes test/apply-changes/input-data.osm test/apply-changes/input-change.osc -f osh\nwarning: GDB can't find the start of the function at 0x77fc6b8c.\n\n    GDB is unable to find the start of the function at 0x77fc6b8c\nand thus can't determine the size of that function's stack frame.\nThis means that GDB may be unable to access that stack frame, or\nthe frames below it.\n    This problem is most likely caused by an invalid program counter or\nstack pointer.\n    However, if you think GDB should simply search farther back\nfrom 0x77fc6b8c for code which looks like the beginning of a\nfunction, you can increase the range of the search using the `set\nheuristic-fence-post' command.\n[Thread debugging using libthread_db enabled]\nUsing host libthread_db library \"/lib/mips-linux-gnu/libthread_db.so.1\".\nwarning: GDB can't find the start of the function at 0x77fc7648.\n\nProgram received signal SIGSEGV, Segmentation fault.\n0x5559bd80 in main (argc=6, argv=<optimized out>) at ./src/main.cpp:111\n111             std::cerr << e.what() << std::endl;\n(gdb) bt full\n#0  0x5559bd80 in main (argc=6, argv=<optimized out>) at ./src/main.cpp:111\n        e = @0x0: <incomplete type>\n        command = \"apply-changes\"\n        arguments = std::vector of length 4, capacity 8 = {\"test/apply-changes/input-data.osm\", \"test/apply-changes/input-change.osc\", \"-f\", \"osh\"}\n        cmd = std::unique_ptr<Command> containing 0x556879a0\n```\n\ncheck-apply-changes-mixed2:\n\n```\n(gdb) run \nStarting program: /home/sebastic/git/pkg-grass/osmium-tool-1.4.0/obj-mips-linux-gnu/src/osmium apply-changes test/apply-changes/input-data.osh test/apply-changes/input-change.osc -f osm\nwarning: GDB can't find the start of the function at 0x77fc6b8c.\n\n    GDB is unable to find the start of the function at 0x77fc6b8c\nand thus can't determine the size of that function's stack frame.\nThis means that GDB may be unable to access that stack frame, or\nthe frames below it.\n    This problem is most likely caused by an invalid program counter or\nstack pointer.\n    However, if you think GDB should simply search farther back\nfrom 0x77fc6b8c for code which looks like the beginning of a\nfunction, you can increase the range of the search using the `set\nheuristic-fence-post' command.\n[Thread debugging using libthread_db enabled]\nUsing host libthread_db library \"/lib/mips-linux-gnu/libthread_db.so.1\".\nwarning: GDB can't find the start of the function at 0x77fc7648.\n\nProgram received signal SIGSEGV, Segmentation fault.\n0x5559bd80 in main (argc=6, argv=<optimized out>) at ./src/main.cpp:111\n111             std::cerr << e.what() << std::endl;\n(gdb) bt full\n#0  0x5559bd80 in main (argc=6, argv=<optimized out>) at ./src/main.cpp:111\n        e = @0x0: <incomplete type>\n        command = \"apply-changes\"\n        arguments = std::vector of length 4, capacity 8 = {\"test/apply-changes/input-data.osh\", \"test/apply-changes/input-change.osc\", \"-f\", \"osm\"}\n        cmd = std::unique_ptr<Command> containing 0x556879a0\n```\n"},"comment":{"url":"https://api.github.com/repos/osmcode/osmium-tool/issues/comments/284972704","html_url":"https://github.com/osmcode/osmium-tool/issues/36#issuecomment-284972704","issue_url":"https://api.github.com/repos/osmcode/osmium-tool/issues/36","id":284972704,"user":{"login":"joto","id":113756,"avatar_url":"https://avatars3.githubusercontent.com/u/113756?v=3","gravatar_id":"","url":"https://api.github.com/users/joto","html_url":"https://github.com/joto","followers_url":"https://api.github.com/users/joto/followers","following_url":"https://api.github.com/users/joto/following{/other_user}","gists_url":"https://api.github.com/users/joto/gists{/gist_id}","starred_url":"https://api.github.com/users/joto/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joto/subscriptions","organizations_url":"https://api.github.com/users/joto/orgs","repos_url":"https://api.github.com/users/joto/repos","events_url":"https://api.github.com/users/joto/events{/privacy}","received_events_url":"https://api.github.com/users/joto/received_events","type":"User","site_admin":false},"created_at":"2017-03-08T07:58:25Z","updated_at":"2017-03-08T07:58:25Z","body":"The current libosmium/osmium-tool code contains some build changes that will explicitly set the `-pthreads` option on the compiler which somebody needed. As this bug seems to be related to threading, maybe it helps here, too."}}
{"actor":{"display_login":"joto"}}