Subject: Re: [bug-diffutils] bug#77840: Testing diffutils 3.12 on PPC Mac OS X 10.4.11, Tiger, produces so many failures

From: Peter Dyballa <[email-masked]>
Date: Sun, 15 Jun 2025 16:59:21 +0200

> Am 13.06.2025 um 00:14 schrieb Paul Eggert <[email-masked]>:
> 
> On 2025-06-12 03:29, Peter Dyballa wrote:
>> (gdb) p base
>> $2 = 0x0
> 
> That's obviously wrong; 'base' should not be a null pointer. Can you track down why it is a null pointer?

I am seeing something strange on my old PPC Tiger Mac:

	run  -> Breakpoint 2, pr_unidiff_hunk (hunk=0x4014d0) at context.c:349
	step -> begin_output () at util.c:797
			util.c:875      outfile = stdout;
	step -> print_context_header (inf=0x599c0, names=0xbfffcdb4, unidiff=true) at context.c:97
	--- Portfile-graphite2-312	2025-06-09 15:48:08.000000000 +0200
	+++ Portfile-graphite2	2025-06-09 15:48:08.000000000 +0200
	next -> begin_output () at util.c:890

	next -> 0x00053d20 in restGPRx ()
	next ->
		Single stepping until exit from function restGPRx, 
		which has no line number information.
		pr_unidiff_hunk (hunk=0x4014d0) at context.c:350

	step -> print_unidiff_number_range (file=0x599c0, a=-4, b=9) at context.c:303
	next -> pr_unidiff_hunk (hunk=0x4014d0) at context.c:355
	step -> print_unidiff_number_range (file=0x59a84, a=-13, b=9) at context.c:303
	next -> pr_unidiff_hunk (hunk=0x4014d0) at context.c:357
	next
	@@ -27,14 +18,23 @@

The central block of lines looks suspicious to me, restGPRx does not exist in diffutils' code. Is this something that could cause a failure later? Next line of output is at least output…

--
Greetings

  Pete

Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.
				– Albert Einstein