Found possible bug - how to report

[Jørn Åne]

Hi, i'm fairly new to FreeBSD and i've never submitted a bugreport
before. I think I found a bug but i'm not sure which component is to blame.

My setup is as follows:

I use winbind for user accounts, my /etc/nsswitch.conf has the following
modifications:
group: winbind files
passwd: winbind files

The problem occurs in csh or tcsh. When I run a program (not a shell
built-in command), the shell goes into a state that will cause it to
exit when I press ^C. So for example:

% ^C
% which which
which: shell built-in command.
% ^C
% which whoami
/usr/bin/whoami
% ^C
% whoami
jornane
% ^CConnection closed.

(^C isn't actually printed, I've added it for clarity)

This does not happen in sh-based shells, and it does not happen when I
change nsswitch back to dist. This problem could be related to
tcsh/csh, nsswitch or samba. I've tried ktrace, but i'm not that good
at reading the output of kdump, and i'm wary of posting the output here
since I don't understand what i'm actually sharing.

Any tips on how I can make a good bug report out of this would be
greatly appreciated!

--
Jørn Åne

[Olivier Nicole]

Jørn Åne,

Post by Jørn Åne
The problem occurs in csh or tcsh. When I run a program (not a shell
built-in command), the shell goes into a state that will cause it to

A similar question pops up regularly, if this is the same problem, one
solution is explained at. I know that the bug description is not very
clear, but it solved my problem.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208132

If my memory serves me right, I had to edit
/usr/src/bin/csh/config_p.h and replace on line 37:

#define VFORK

by

/* #define VFORK */
#define vfork fork

The make, make install.

Best regards,

Olivier

Post by Jørn Åne
Hi, i'm fairly new to FreeBSD and i've never submitted a bugreport
before. I think I found a bug but i'm not sure which component is to blame.
I use winbind for user accounts, my /etc/nsswitch.conf has the following
group: winbind files
passwd: winbind files
The problem occurs in csh or tcsh. When I run a program (not a shell
built-in command), the shell goes into a state that will cause it to
% ^C
% which which
which: shell built-in command.
% ^C
% which whoami
/usr/bin/whoami
% ^C
% whoami
jornane
% ^CConnection closed.
(^C isn't actually printed, I've added it for clarity)
This does not happen in sh-based shells, and it does not happen when I
change nsswitch back to dist. This problem could be related to
tcsh/csh, nsswitch or samba. I've tried ktrace, but i'm not that good
at reading the output of kdump, and i'm wary of posting the output here
since I don't understand what i'm actually sharing.
Any tips on how I can make a good bug report out of this would be
greatly appreciated!
--
Jørn Åne
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions

[Bernt Hansson]

Post by Jørn Åne
Hi, i'm fairly new to FreeBSD and i've never submitted a bugreport
before. I think I found a bug but i'm not sure which component is to blame.
I use winbind for user accounts, my /etc/nsswitch.conf has the following
group: winbind files
passwd: winbind files
The problem occurs in csh or tcsh. When I run a program (not a shell
built-in command), the shell goes into a state that will cause it to
% ^C
% which which
which: shell built-in command.
% ^C
% which whoami
/usr/bin/whoami
% ^C
% whoami
jornane
% ^CConnection closed.
(^C isn't actually printed, I've added it for clarity)
This does not happen in sh-based shells, and it does not happen when I
change nsswitch back to dist.

It does happen in sh based shells. Csh and tcsh are both sh based.

[Michael Schuster]

Post by Bernt Hansson
Csh and tcsh are both sh based.

that's a rather surprising statement. Can you support it? (It goes against
most I ever heard about csh - I was under the impression that Bill Joy
wrote csh while at university because he was fed up with how sh worked, but
that may be wrong [too?]).

Michael

[Jørn Åne]

Post by Olivier Nicole
Jørn Åne,

Post by Jørn Åne
The problem occurs in csh or tcsh. When I run a program (not a shell
built-in command), the shell goes into a state that will cause it to

A similar question pops up regularly, if this is the same problem, one
solution is explained at. I know that the bug description is not very
clear, but it solved my problem.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208132

Yep, that's the one! Making the proposed change fixes the bug for me.

Thanks

--
Jørn Åne

[krad]

My understanding was bash was the next gen sh, as tcsh was the next csh....

Post by Michael Schuster

Post by Bernt Hansson
Csh and tcsh are both sh based.

that's a rather surprising statement. Can you support it? (It goes against
most I ever heard about csh - I was under the impression that Bill Joy
wrote csh while at university because he was fed up with how sh worked, but
that may be wrong [too?]).
Michael
--
Michael Schuster
http://recursiveramblings.wordpress.com/
recursion, n: see 'recursion'
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "

[Bernt Hansson]

Post by Michael Schuster

Post by Bernt Hansson
Csh and tcsh are both sh based.

that's a rather surprising statement. Can you support it? (It goes against
most I ever heard about csh - I was under the impression that Bill Joy
wrote csh while at university because he was fed up with how sh worked, but
that may be wrong [too?]).
Michael

Well you supported it yourself.

[Michael Schuster]

Post by Bernt Hansson

Post by Bernt Hansson
Csh and tcsh are both sh based.
that's a rather surprising statement. Can you support it? (It goes against
most I ever heard about csh - I was under the impression that Bill Joy
wrote csh while at university because he was fed up with how sh worked,
but
that may be wrong [too?]).
Michael

Well you supported it yourself.

can you elaborate? I thought I actually did exactly the opposite ...
ETOOLITTLECOFFEE?

cheers
Michael