On Tue, Jul 11, 2023 at 09:13:38PM +0200, Theo Buehler wrote:
> On Tue, Jul 11, 2023 at 08:35:31PM +0200, Theo Buehler wrote:
> > On Tue, Jul 11, 2023 at 02:32:48PM +0200, Theo Buehler wrote:
> > > On Tue, Jul 11, 2023 at 11:48:57AM +0100, Stuart Henderson wrote:
> > > > I ran into a segfault with
looks reasonable.
OK florian
On 2023-07-11 21:13 +02, Theo Buehler wrote:
> On Tue, Jul 11, 2023 at 08:35:31PM +0200, Theo Buehler wrote:
>> On Tue, Jul 11, 2023 at 02:32:48PM +0200, Theo Buehler wrote:
>> > On Tue, Jul 11, 2023 at 11:48:57AM +0100, Stuart Henderson wrote:
>> > > I ran into a se
On Tue, Jul 11, 2023 at 08:35:31PM +0200, Theo Buehler wrote:
> On Tue, Jul 11, 2023 at 02:32:48PM +0200, Theo Buehler wrote:
> > On Tue, Jul 11, 2023 at 11:48:57AM +0100, Stuart Henderson wrote:
> > > I ran into a segfault with patch(1) in a port, here's a test case with a
> > > minimal reproducer
On Tue, Jul 11, 2023 at 02:32:48PM +0200, Theo Buehler wrote:
> On Tue, Jul 11, 2023 at 11:48:57AM +0100, Stuart Henderson wrote:
> > I ran into a segfault with patch(1) in a port, here's a test case with a
> > minimal reproducer.
> >
> > $ echo foo > test
> > $ perl -e 'print "--- test.orig\n+++
On Tue, Jul 11, 2023 at 11:48:57AM +0100, Stuart Henderson wrote:
> I ran into a segfault with patch(1) in a port, here's a test case with a
> minimal reproducer.
>
> $ echo foo > test
> $ perl -e 'print "--- test.orig\n+++ test\n@@ -1,1 +1,2 @@\n foo\n+" . 'x' x
> 32768 . "\n\\ No newline at end
I ran into a segfault with patch(1) in a port, here's a test case with a
minimal reproducer.
$ echo foo > test
$ perl -e 'print "--- test.orig\n+++ test\n@@ -1,1 +1,2 @@\n foo\n+" . 'x' x
32768 . "\n\\ No newline at end of file\n"' > test.patch
$ patch < test.patch
Hmm... Looks like a unified di
