Package Details: tudu-git r273.700cd21-1

Git Clone URL: (read-only, click to copy)
Package Base: tudu-git
Description: ncurses-based hierarchical todo list manager with vim-like keybindings
Upstream URL:
Licenses: GPL
Conflicts: tudu
Provides: tudu
Submitter: ahphaw5S
Maintainer: ahphaw5S
Last Packager: ahphaw5S
Votes: 1
Popularity: 0.000000
First Submitted: 2016-03-08 08:16
Last Updated: 2019-07-20 22:02

Latest Comments

handles commented on 2016-10-10 09:42

Anyone got this working? i tried the latest build and still getting segfaults.

handles commented on 2016-07-27 11:17

debug with gdb
Program received signal SIGSEGV, Segmentation fault. |
0x00007ffff7b9ed92 in ?? () from /usr/lib/

handles commented on 2016-06-28 23:57

So i just compiled:
--without=O2 --without=fstack-protector-strong
Still seg faults :(

ahphaw5S commented on 2016-06-28 05:47

I actually just cloned repository, compiled and run it (I have also installed the package itself, separately, otherwise it complains that there is a global configuration file is missing).

I think if I compile it without any changes to a given in the repository Makefile, then everything is fine.

But if I try to put extra flags (like -fstack-protector-strong, and (sorry made a mistake last time) *without* -O2 then I have got sigfaults).

handles commented on 2016-06-27 13:20

Sorry, noob moments. How do execute tudu once i have compiled it with different options. Even tho --prefix=/usr --sysconfdir=/etc, it fails to start with passing tudu on the cli and there is no /usr/bin/tudu.

ahphaw5S commented on 2016-06-21 07:20

It would be nice if you could confirm that compilation with -O2 and without -fstack-protector-strong gives no segfault, and compilation with -O2 and with -fstack-protector-strong leads to a corruption. Because I manage to do it on my machine, but unfortumately the author of tudu wasn't able to reproduce it.

I shall try to have another go on this problem in the next few days.

handles commented on 2016-06-21 05:23

Anything i can do to help?

ahphaw5S commented on 2016-06-20 07:00

Yes, unfortunately there is a bug somewhere in a program itself. I just managed to find out that compiling without flag -fstack-protector-strong makes it work without segfaults.

handles commented on 2016-06-19 12:24

Still getting Seg-faults...