New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TI-39] Bogus command line option causes segfault #44

Closed
taskwarrior opened this Issue Feb 11, 2018 · 3 comments

Comments

Projects
None yet
1 participant
@taskwarrior

taskwarrior commented Feb 11, 2018

Jan Stolarek on 2016-09-01T20:05:03Z says:

When I pass a bogus string as value of rc.reports.week.lines I get a segfault:

{code}
[killy(at)GLaDOS : ~] tw week rc.reports.week.lines=foobar

       0    1    2    3    4    5    6    7    8    9    10   11   12   13   14   15   16   17   18   19   20   21   22   23     Total

Segmentation fault
{code}

@taskwarrior taskwarrior added this to the 1.1.0 milestone Feb 11, 2018

@taskwarrior

This comment has been minimized.

taskwarrior commented Feb 11, 2018

Migrated metadata:

Created: 2016-09-01T20:05:03Z
Modified: 2017-02-13T21:05:20Z
@taskwarrior

This comment has been minimized.

taskwarrior commented Feb 11, 2018

Jelle van der Waa on 2016-09-05T18:52:14Z says:

Same segfault occurs with the following command:
{code}
timew week monday rc.reports.week.cell=wefjiwf
{code}

@taskwarrior

This comment has been minimized.

taskwarrior commented Feb 11, 2018

Thomas Lauf on 2017-02-13T20:40:40Z says:

Parsing strings like 'foobar' or 'wefjiwf' as integer returns 0. Segfault occurs if this value is used to divide by or create an array (with size 0) and access its first element.

This is now fixed such that TimeWarrior returns an error message about an invalid configuration value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment