View Issue Details

IDProjectCategoryView StatusLast Update
0002482GNUnetfile-sharing servicepublic2012-11-05 18:33
ReporterLRN Assigned ToChristian Grothoff  
PrioritylowSeveritycrashReproducibilityhave not tried
Status closedResolutionunable to reproduce 
Product VersionGit master 
Target Version0.9.4Fixed in Version0.9.4 
Summary0002482: Crash in FS service when it is shut down early
Descriptionr22475+7
Steps To Reproducerun `gnunet-arm s'
then run `gnunet-arm -e' shortly after that.
Additional Information
Program received signal SIGSEGV, Segmentation fault.
0x00406078 in GSF_peer_transmit_cancel_ (pth=0xdf0adba) at gnunet-service-fs_cp.c:1433
1433      if (pth->timeout_task != GNUNET_SCHEDULER_NO_TASK)
(gdb) bt
#0  0x00406078 in GSF_peer_transmit_cancel_ (pth=0xdf0adba) at gnunet-service-fs_cp.c:1433
#1  0x0040babc in schedule_peer_transmission (cls=0x1d9c868, tc=0x28fc80) at gnunet-service-fs_pe.c:444
#2  0x62af7dcf in run_ready (rs=0x4ecde0, ws=0x4eddf8) at scheduler.c:608
#3  0x62af8576 in GNUNET_SCHEDULER_run (task=0x62b0475e <service_task>, task_cls=0x28fe20) at scheduler.c:796
#4  0x62b0549a in GNUNET_SERVICE_run (argc=3, argv=0x1d7bd58, service_name=0x417167 "fs", options=GNUNET_SERVICE_OPTION_NONE, task=0x401e24 <run>,
    task_cls=0x0) at service.c:1788
#5  0x00402050 in main (argc=3, argv=0x1d7bd58) at gnunet-service-fs.c:650
(gdb) p pth
$1 = (struct GSF_PeerTransmitHandle *) 0xdf0adba
(gdb) up
#1  0x0040babc in schedule_peer_transmission (cls=0x1d9c868, tc=0x28fc80) at gnunet-service-fs_pe.c:444
444         GSF_peer_transmit_cancel_ (pp->pth);
(gdb) p *pp
$2 = {priority_heap = 0xdf0003e, delay_heap = 0xdf0adba, plan_map = 0xdf0adba, pth = 0xdf0adba, cp = 0xdf0adba, task = 0}
TagsNo tags attached.

Activities

Christian Grothoff

2012-07-05 19:13

manager   ~0006215

I cannot reproduce this (tried many times, with and without valgrind).

LRN

2012-07-05 21:40

reporter   ~0006216

I was running with GNUNET_FORCE_LOG=";;;;DEBUG".
Though i don't think this is a significant factor: i ran gnunet-namestore -D after starting the node, before shutting it down. That takes, like, 3 seconds.

Christian Grothoff

2012-07-18 00:10

manager   ~0006258

I've tried it more, still no luck.

Issue History

Date Modified Username Field Change
2012-07-04 21:26 LRN New Issue
2012-07-05 08:54 Christian Grothoff Assigned To => Christian Grothoff
2012-07-05 08:54 Christian Grothoff Status new => assigned
2012-07-05 19:13 Christian Grothoff Note Added: 0006215
2012-07-05 19:13 Christian Grothoff Status assigned => feedback
2012-07-05 21:40 LRN Note Added: 0006216
2012-07-05 21:40 LRN Status feedback => assigned
2012-07-18 00:10 Christian Grothoff Note Added: 0006258
2012-07-18 00:10 Christian Grothoff Assigned To Christian Grothoff =>
2012-07-18 00:10 Christian Grothoff Status assigned => feedback
2012-09-17 12:58 Christian Grothoff Priority normal => low
2012-11-04 22:37 Christian Grothoff Assigned To => Christian Grothoff
2012-11-04 22:37 Christian Grothoff Status feedback => resolved
2012-11-04 22:37 Christian Grothoff Resolution open => unable to reproduce
2012-11-04 22:37 Christian Grothoff Fixed in Version => 0.9.4
2012-11-04 22:37 Christian Grothoff Target Version => 0.9.4
2012-11-05 18:33 Christian Grothoff Status resolved => closed