public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Sam Warner <samuel.r.warner@me.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb@sourceware.org
Subject: Re: GDB and MacOS 11.4/BigSur
Date: Tue, 29 Jun 2021 07:38:38 -0700	[thread overview]
Message-ID: <84DA278D-49EE-4624-B292-F1EFF2B66A43@me.com> (raw)
In-Reply-To: <87919838-2470-33d6-f9f6-2dde5b271fcc@polymtl.ca>

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


  reply	other threads:[~2021-06-29 14:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-26 18:40 Sam Warner
2021-06-26 23:08 ` Simon Marchi
2021-06-26 23:27   ` Sam Warner
2021-06-27  0:51     ` Simon Marchi
2021-06-27  4:00       ` Simon Marchi
2021-06-27 20:32       ` Sam Warner
2021-06-27 22:27         ` Simon Marchi
2021-06-27 22:44           ` Sam Warner
2021-06-28  0:48             ` Simon Marchi
2021-06-28 18:10               ` Sam Warner
2021-06-28 21:51               ` Sam Warner
2021-06-29  0:03                 ` Sam Warner
2021-06-29  0:29                   ` Sam Warner
2021-06-29  1:34                     ` Sam Warner
2021-06-29  1:44                       ` Sam Warner
2021-06-29 14:04                         ` Simon Marchi
2021-06-29 14:38                           ` Sam Warner [this message]
2021-06-29 14:43                             ` Simon Marchi
2021-06-29 14:45                               ` Sam Warner
2021-06-29 14:59                                 ` Sam Warner
2021-06-29 15:17                                   ` Sam Warner
2021-06-29 15:23                                     ` Simon Marchi
2021-06-30 21:29                                       ` Sam Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84DA278D-49EE-4624-B292-F1EFF2B66A43@me.com \
    --to=samuel.r.warner@me.com \
    --cc=gdb@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).