Thread View: gnu.bash.bug
2 messages
2 total messages
Started by Andrew Thomas
Mon, 13 Nov 1989 17:31
Bind patch errors - free dumps core
Author: Andrew Thomas
Date: Mon, 13 Nov 1989 17:31
Date: Mon, 13 Nov 1989 17:31
14 lines
917 bytes
917 bytes
Regarding the patches posted recently for bind, I have some complaints. any attempt to rebind a macro, either to nil or to a different key string results in a core dump due to free being called on an invalid pointer and a message to bfox, which I am sure he does not want to see. Any information on how to fix this would be appreciated. Thanks, -- Andrew Thomas andrewt@watsnew.waterloo.edu Systems Design Eng. University of Waterloo "If a million people do a stupid thing, it's still a stupid thing." - Opus
Re: Bind patch errors - free dumps core
Author: Trip Martin
Date: Tue, 14 Nov 1989 16:20
Date: Tue, 14 Nov 1989 16:20
20 lines
1386 bytes
1386 bytes
In <ANDREWT.89Nov13123127@watsnew.waterloo.edu> andrewt@watsnew.waterloo.edu (Andrew Thomas) writes: > >Regarding the patches posted recently for bind, I have some >complaints. any attempt to rebind a macro, either to nil or to a >different key string results in a core dump due to free being called >on an invalid pointer and a message to bfox, which I am sure he does >not want to see. Any information on how to fix this would be >appreciated. Those patches were not meant to be posted. I was replying to Brian, and didn't notice the cc to gnu-bash-bug. My apologies for any problems it may cause. I'll be more careful in the future. I'll look into the bug though. Also, you can't do a macro bind to nil. It should give you an error for that. If you want to disable a key, do a function bind to nil (i.e. no "macro" keyword). -- Trip Martin KA2LIV night@pawl.rpi.edu Finite state machinist night@uruguay.acm.rpi.edu
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads