GDB and MacOS 11.4/BigSur

[Sam Warner]

Is there a before review checklist?
Seems it would have:
1) use change in the latest source tree, presumably on all supported OSes, and log build
2) use test-suite before, and on all supported OSes, log results
3) fix test on all supported on all supported OSe

Which, for me, the all supported OSes is the big hurdle (in time and logistics). How’s this solved?

For now, I repro’ed the null-pointer issue is in the build I generated, which is good news,  I’ll grab that source fix you supplied and see if it resolves the issue.

Sam



> On Jun 29, 2021, at 7:04 AM, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> 
> On 2021-06-28 9:44 p.m., Sam Warner wrote:
>> Hi Simon,
>>   Thank you - the added details you gave me really helped, especially when I both obtained the official 10.2 source set, and followed the BuildingForDarwin <https://sourceware.org/gdb/wiki/BuildingOnDarwin> instructions for  ".configure --disable-intl”.
> 
> If you intend to make changes that you want integrated upstream, you
> should really work using the latest git (and keep it up to date), not
> 10.2.
> 
> That wiki page is really old, it could really use a refresh.
> 
>>  I successfully built now, and off to use the test-suites
> 
> Glad to hear it.
> 
> You can do some manual some tests first, trying to debug a little
> program.  If that works, to run the testsuite:
> 
>  https://sourceware.org/gdb/wiki/TestingGDB
> 
> However, I expect it to be in a really bad shape on macOS (if you can
> get it to run at all) and would need quite a lot of effort to run
> relatively clean.  But all efforts start with a baby step, so if you can
> get at least a small test to run it would be great already.  For
> example, getting the gdb.base/template.exp test to run (it's kind of a
> "Hello World!" test, serving as an example when writing a test from
> scratch.  So you would use:
> 
>  $ make check TESTS="gdb.base/template.exp"
> 
> Simon