really bad dj(1) bugs #139

Closed
opened 2024-07-10 00:28:05 -06:00 by emma · 5 comments
Owner
$ dj -B 256 -c 1 -i /dev/urandom -o file 
zsh: segmentation fault  dj -B 256 -c 1 -i /dev/urandom -o file

This segfaults on my Linux system but creates a file upward of 250kB on my OpenBSD system.

This behavior is in the current version of the main branch.

``` $ dj -B 256 -c 1 -i /dev/urandom -o file zsh: segmentation fault dj -B 256 -c 1 -i /dev/urandom -o file ``` This segfaults on my Linux system but creates a `file` upward of 250kB on my OpenBSD system. This behavior is in the current version of the main branch.
emma added the
bug
label 2024-07-10 00:28:05 -06:00
trinity was assigned by emma 2024-07-10 00:28:05 -06:00
Author
Owner

There are more issues with the vagueness of the dj.1 manpage I also want to clear up that I only encountered once trying to use it for practical purposes.

There are more issues with the vagueness of the `dj.1` manpage I also want to clear up that I only encountered once trying to use it for practical purposes.
Owner

just took a look at the dj code and honestly it's pretty grody in its current state. this has motivated the filing of #140, which should hopefully make the c code in the tree a little more maintainable in the future.

just took a look at the dj code and honestly it's pretty grody in its current state. this has motivated the filing of https://git.tebibyte.media/bonsai/harakit/issues/140, which should hopefully make the c code in the tree a little more maintainable in the future.
Owner

Does this bug exist on the dj branch?

Does this bug exist on the dj branch?
Owner

worth mentioning that dj works fine on both branches for me, not sure where the inconsistency would come from.

worth mentioning that dj works fine on both branches for me, not sure where the inconsistency would come from.
Author
Owner

Does this bug exist on the dj branch?

It does not.

> Does this bug exist on the dj branch? It does not.
emma closed this issue 2024-07-15 14:02:22 -06:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: bonsai/harakit#139
No description provided.