View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005586 | GNUnet | file-sharing service | public | 2019-02-19 02:05 | 2019-02-28 11:17 |
Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
Priority | urgent | Severity | crash | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
Product Version | Git master | ||||
Target Version | 0.11.0 | Fixed in Version | 0.11.0 | ||
Summary | 0005586: valgrind-related crash in FS testcase | ||||
Description | test_gnunet_service_fs_p2p_cadet.log:==98000== Invalid read of size 8 test_gnunet_service_fs_p2p_cadet.log:==98000== at 0x48AE518: GNUNET_CADET_channel_destroy (cadet_api.c:953) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11FCF6: cadet_timeout (gnunet-service-fs_cadet_client.c:521) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x492E4E2: GNUNET_SCHEDULER_do_work (scheduler.c:2115) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x492F35A: select_loop (scheduler.c:2412) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x49299F9: GNUNET_SCHEDULER_run (scheduler.c:727) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x4936DEF: GNUNET_SERVICE_run_ (service.c:2449) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11038C: main (gnunet-service-fs.c:1384) test_gnunet_service_fs_p2p_cadet.log:==98000== Address 0x54d6e40 is 32 bytes inside a block of size 112 free'd test_gnunet_service_fs_p2p_cadet.log:==98000== at 0x48369AB: free (vg_replace_malloc.c:530) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x48E28E4: GNUNET_xfree_ (common_allocation.c:339) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x48AC831: destroy_channel (cadet_api.c:304) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x48AE5F6: GNUNET_CADET_channel_destroy (cadet_api.c:968) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x120CB5: GSF_cadet_release_clients (gnunet-service-fs_cadet_client.c:744) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x48F285D: GNUNET_CONTAINER_multipeermap_iterate (container_multipeermap.c:365) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x122231: GSF_cadet_stop_server (gnunet-service-fs_cadet_server.c:527) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x10F710: shutdown_task (gnunet-service-fs.c:1173) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x492E4E2: GNUNET_SCHEDULER_do_work (scheduler.c:2115) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x492F35A: select_loop (scheduler.c:2412) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x49299F9: GNUNET_SCHEDULER_run (scheduler.c:727) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x4936DEF: GNUNET_SERVICE_run_ (service.c:2449) test_gnunet_service_fs_p2p_cadet.log:==98000== Block was alloc'd at test_gnunet_service_fs_p2p_cadet.log:==98000== at 0x483577F: malloc (vg_replace_malloc.c:299) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x48E25C0: GNUNET_xmalloc_unchecked_ (common_allocation.c:232) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x48E1F5C: GNUNET_xmalloc_ (common_allocation.c:75) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x48AC4E2: create_channel (cadet_api.c:244) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x48AEEF4: GNUNET_CADET_channel_create (cadet_api.c:1155) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x1204A7: get_cadet (gnunet-service-fs_cadet_client.c:630) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x12057A: GSF_cadet_query (gnunet-service-fs_cadet_client.c:667) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11B958: GSF_cadet_lookup_ (gnunet-service-fs_pr.c:1295) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x10DF0B: start_p2p_processing (gnunet-service-fs.c:769) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11BD16: call_continuation (gnunet-service-fs_pr.c:1381) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11BDAF: no_more_local_results (gnunet-service-fs_pr.c:1399) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11C038: process_local_reply (gnunet-service-fs_pr.c:1512) test_gnunet_service_fs_p2p_cadet.log:==98000== test_gnunet_service_fs_p2p_cadet.log:==98000== Invalid read of size 8 test_gnunet_service_fs_p2p_cadet.log:==98000== at 0x48AE524: GNUNET_CADET_channel_destroy (cadet_api.c:957) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11FCF6: cadet_timeout (gnunet-service-fs_cadet_client.c:521) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x492E4E2: GNUNET_SCHEDULER_do_work (scheduler.c:2115) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x492F35A: select_loop (scheduler.c:2412) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x49299F9: GNUNET_SCHEDULER_run (scheduler.c:727) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x4936DEF: GNUNET_SERVICE_run_ (service.c:2449) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11038C: main (gnunet-service-fs.c:1384) test_gnunet_service_fs_p2p_cadet.log:==98000== Address 0xdf0adba0df0adba is not stack'd, malloc'd or (recently) free'd test_gnunet_service_fs_p2p_cadet.log:==98000== test_gnunet_service_fs_p2p_cadet.log:==98000== test_gnunet_service_fs_p2p_cadet.log:==98000== Process terminating with default action of signal 11 (SIGSEGV): dumping core test_gnunet_service_fs_p2p_cadet.log:==98000== General Protection Fault test_gnunet_service_fs_p2p_cadet.log:==98000== at 0x48AE524: GNUNET_CADET_channel_destroy (cadet_api.c:957) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11FCF6: cadet_timeout (gnunet-service-fs_cadet_client.c:521) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x492E4E2: GNUNET_SCHEDULER_do_work (scheduler.c:2115) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x492F35A: select_loop (scheduler.c:2412) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x49299F9: GNUNET_SCHEDULER_run (scheduler.c:727) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x4936DEF: GNUNET_SERVICE_run_ (service.c:2449) test_gnunet_service_fs_p2p_cadet.log:==98000== by 0x11038C: main (gnunet-service-fs.c:1384) | ||||
Tags | No tags attached. | ||||
|
Is this required to be solved in 0.11.0? Are you planning to keep the 28th as the release date and add minor bugs to be solved on that roadmap? |
|
This time is deliberately used for stabilization / testing, and as I intend to fix this bug (which should be reasonably easy) today, of course it is now on the map for 0.11. If you are _sure_ to fix bugs by Feb 28th, you can add them to the roadmap as well. Or if you find something that is really so bad that it must be fixed beforehand. And this one is both feasible and IMO critical. |
|
Fixed in 2caf34724..25333278f |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-02-19 02:05 | Christian Grothoff | New Issue | |
2019-02-19 02:05 | Christian Grothoff | Status | new => assigned |
2019-02-19 02:05 | Christian Grothoff | Assigned To | => Christian Grothoff |
2019-02-19 10:37 | nikita | Note Added: 0013870 | |
2019-02-19 10:42 | Christian Grothoff | Note Added: 0013871 | |
2019-02-19 10:53 | Christian Grothoff | Status | assigned => resolved |
2019-02-19 10:53 | Christian Grothoff | Resolution | open => fixed |
2019-02-19 10:53 | Christian Grothoff | Fixed in Version | => 0.11.0 |
2019-02-19 10:53 | Christian Grothoff | Note Added: 0013873 | |
2019-02-28 11:17 | Christian Grothoff | Status | resolved => closed |