Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15375 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-09-16 11:04 -0400 |
| Last post | 2019-09-16 11:04 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: possible buffer overflow by bad translation Chet Ramey <chet.ramey@case.edu> - 2019-09-16 11:04 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-09-16 11:04 -0400 |
| Subject | Re: possible buffer overflow by bad translation |
| Message-ID | <mailman.357.1568646264.2190.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web