You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And then you do a typeset -p | head -1, everything works fine.
If the first code is run again, it outputs the usual message about not being able to redefine types.
However, then doing a typeset -p | head -1 will work, but also output "Memory fault(coredump)".
If it's run without the | head -1, it segfaults the entire shell.
If the typeset -T Foo_t=... is moved outside of the namespace, the opposite happens: the typeset -p | head -1 will work with the output "Memory fault(coredump)", but just typeset -p will work fine.
I also tested this in 1.0.0-beta.2 (since Ubuntu hasn't updated their version in apt yet...)
For the first case, the typeset -p | head -1 will take a long time but output nothing, and then crash when the | head -1 is removed. However, when the typeset -T Foo_t=... is moved outside of the namespace, no issues at all occur.
The text was updated successfully, but these errors were encountered:
If this code is run in 1.0.10:
And then you do a
typeset -p | head -1
, everything works fine.If the first code is run again, it outputs the usual message about not being able to redefine types.
However, then doing a
typeset -p | head -1
will work, but also output "Memory fault(coredump)".If it's run without the
| head -1
, it segfaults the entire shell.If the
typeset -T Foo_t=...
is moved outside of the namespace, the opposite happens: thetypeset -p | head -1
will work with the output "Memory fault(coredump)", but justtypeset -p
will work fine.I also tested this in 1.0.0-beta.2 (since Ubuntu hasn't updated their version in apt yet...)
For the first case, the
typeset -p | head -1
will take a long time but output nothing, and then crash when the| head -1
is removed. However, when thetypeset -T Foo_t=...
is moved outside of the namespace, no issues at all occur.The text was updated successfully, but these errors were encountered: