ceelog-0.1-1.fc19.i686 % gdb -args ceelog '/.*/' (gdb) run ** (ceelog:15400): CRITICAL **: ceelog_expr_parse: assertion `error == NULL || *error == NULL' failed ceelog: Program received signal SIGSEGV, Segmentation fault. 0x402349fa in _IO_vfprintf_internal (s=0xbfffcd08, format=<optimized out>, ap= 0xbffff39c "e\207\004\b+\237\027@\001") at vfprintf.c:1635 1635 process_string_arg (((struct printf_spec *) NULL)); (gdb) bt #0 0x402349fa in _IO_vfprintf_internal (s=0xbfffcd08, format=<optimized out>, ap=0xbffff39c "e\207\004\b+\237\027@\001") at vfprintf.c:1635 #1 0x402359eb in buffered_vfprintf (s=s@entry=0x403ae980 <_IO_2_1_stderr_>, format=format@entry=0x8048cee "Error compiling %s: %s", args=args@entry= 0xbffff394 "4\366\377\277e3\025\030e\207\004\b+\237\027@\001") at vfprintf.c:2319 #2 0x40230bc5 in _IO_vfprintf_internal (s=s@entry= 0x403ae980 <_IO_2_1_stderr_>, format=format@entry= 0x8048cee "Error compiling %s: %s", ap=ap@entry= 0xbffff394 "4\366\377\277e3\025\030e\207\004\b+\237\027@\001") at vfprintf.c:1289 #3 0x402feee1 in ___vfprintf_chk (fp=0x403ae980 <_IO_2_1_stderr_>, flag=flag@entry=1, format=format@entry=0x8048cee "Error compiling %s: %s", ap=ap@entry=0xbffff394 "4\366\377\277e3\025\030e\207\004\b+\237\027@\001") at vfprintf_chk.c:34 #4 0x0804895a in vfprintf (__ap= 0xbffff394 "4\366\377\277e3\025\030e\207\004\b+\237\027@\001", __fmt= 0x8048cee "Error compiling %s: %s", __stream=<optimized out>) at /usr/include/bits/stdio2.h:127 #5 error_exit (fmt=0x8048cee "Error compiling %s: %s") at src/ceelog.c:40 #6 0x08048b19 in main (argc=2, argv=0xbffff474) at src/ceelog.c:65 (gdb) frame 6 #6 0x08048b19 in main (argc=2, argv=0xbffff474) at src/ceelog.c:65 65 error_exit (_("Error compiling %s: %s"), argv[1], error->message); (gdb) p error $1 = (GError *) 0x4021dbed <__cxa_atexit+29> (gdb) p *error $2 = {domain = 745848965, code = 539251851, message = 0x18153365 <Address 0x18153365 out of bounds>}
It looks like the GError *error; at the top of main() is never initialized.
Created attachment 662196 [details] Patch for ceelog.c to initialize error to NULL Hi, this seems to be a problem that error is not initialized to NULL. This is fixed in git master and will be available in next version. Could you please try this patch to make sure this fixes your problem? Thanks a lot, Milan Bartos
ceelog-0.1-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/ceelog-0.1-3.fc17
Package ceelog-0.1-3.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ceelog-0.1-3.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20701/ceelog-0.1-3.fc17 then log in and leave karma (feedback).
ceelog-0.1-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.