Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15375
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: possible buffer overflow by bad translation |
| Date | 2019-09-16 11:04 -0400 |
| Message-ID | <mailman.357.1568646264.2190.bug-bash@gnu.org> (permalink) |
| References | <7e38edcd-b44f-3287-1406-c7353a74109b@gmx.de> <661901a6-7fa6-8a4f-5297-dc51e400174d@case.edu> |
On 9/15/19 2:24 PM, Roland Illig wrote:
> From siglist.c:
>
> sys_siglist[i] =
> (char *)xmalloc (10 + strlen (_("Unknown Signal #")));
>
> sprintf (sys_siglist[i], _("Unknown Signal #%d"), i);
I'll figure something out. This code is used in exceedingly rare
circumstances: where a system doesn't provide sys_siglist[] or
strsignal(). You probably haven't used one in years.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: possible buffer overflow by bad translation Chet Ramey <chet.ramey@case.edu> - 2019-09-16 11:04 -0400
csiph-web