View Issue Details

IDProjectCategoryView StatusLast Update
0003917GNUnetfile-sharing servicepublic2018-06-06 22:25
Reporterremibd Assigned ToChristian Grothoff Due Date
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version0.10.1 
Target Version0.11.0pre66Fixed in Version0.11.0pre66 
Summary0003917: Simulating publication in a namespace causes a segfault
Description`GNUNET_FS_publish_sks` segfaults when called with options=GNUNET_FS_PUBLISH_OPTION_SIMULATE_ONLY. It impacts `gnunet-publish`.
Steps To Reproduce$ gnunet-publish -s -P <ego> -t <id> <file>
Additional InformationReason of the segfault: fs/fs_namespace.c:460, inside the definition of `GNUNET_FS_publish_sks`, the variable `psc->dsh` is initialized to NULL and it’s value is given to the static function `GNUNET_FS_publish_ublock_`, which will try to dereference it.

--------------------------------------------------------------
OS : Linux
OS RELEASE : 4.1.2-2-ARCH
HARDWARE : x86_64
gcc : gcc (GCC) 5.1.0
make : 4.1
autoconf : 2.69
automake : 1.15
libtool : 2.4.6
libextractor : v1.0.1
GNUnet 0.8 : Not Found (good)
GNUnet 0.9 : 0.10.1
libgcrypt : 1.6.3
mysql : Not Found
pkg-config : 0.28
glib2 : 2.44.1
gtk2+ : 2.24.28
GMP : Test not available
libunistring : Test not available
GNU gettext : 0.19.4
libcurl : 7.43.0
libgnurl : 7.40.0
libmicrohttpd : 94200
GNU GLPK : Not found
GNUtls : 3.4.2
--------------------------------------------------------------
TagsNo tags attached.

Activities

Christian Grothoff

2015-07-27 12:39

manager   ~0009486

I've looked at the code AND tried to reproduce it, and I cannot.

The GNUNET_FS_publish_ublock_ function in my code DOES check for dsh being NULL, the check was introduced in SVN 33766 (June 23rd, 2014):

http://lists.gnu.org/archive/html/gnunet-svn/2014-06/msg00309.html

My guess is that you're running 0.10.1 instead of using Subversion and are thus missing out on hundreds of bugfixes...

Christian Grothoff

2015-08-03 11:38

manager   ~0009522

No feedback from remibd after almost a week, assuming he was using 0.10.1 and this was already resolved.

Issue History

Date ModifiedUsernameFieldChange
2015-07-25 13:56remibdNew Issue
2015-07-27 12:39Christian GrothoffNote Added: 0009486
2015-07-27 12:39Christian GrothoffAssigned To => Christian Grothoff
2015-07-27 12:39Christian GrothoffStatusnew => feedback
2015-07-27 12:39Christian GrothoffProduct Version => 0.10.1
2015-07-27 12:39Christian GrothoffTarget Version => 0.11.0pre66
2015-08-03 11:38Christian GrothoffNote Added: 0009522
2015-08-03 11:38Christian GrothoffStatusfeedback => resolved
2015-08-03 11:38Christian GrothoffFixed in Version => 0.11.0pre66
2015-08-03 11:38Christian GrothoffResolutionopen => no change required
2018-06-06 22:25Christian GrothoffStatusresolved => closed