[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Out of bounds read in parse.y.
From: |
Collin Funk |
Subject: |
Re: Out of bounds read in parse.y. |
Date: |
Tue, 27 Aug 2024 12:58:15 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hi Chet,
Chet Ramey <chet.ramey@case.edu> writes:
> Which version?
This was from bash devel branch, commit hash
2e01122fe78eb5a42c9b9f3ca46b91f895959675.
Built with:
./configure CFLAGS='-fsanitize=undefined'
> Why? 0 is a valid index. set_word_top increments word_top before assigning
> to word_lineno[word_top].
Ah, okay. I see what you mean.
> I suspect there is a decrement that isn't matched by a call to
> set_word_top(). But a reproducer would help, otherwise we're all just
> guessing.
Sure, the bad read was happening while reading my .profile and .bashrc
file. I've narrowed it down to a bash completion file installed by my
system packages. I've attached it to this message.
Running:
./bash --norc ovs-vsctl-bashcomp.bash
triggers the out of bounds read.
ovs-vsctl-bashcomp.bash
Description: Text document