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: Mon, 28 Jun 2021 17:03:19 -0700 [thread overview]
Message-ID: <810B4416-EE0C-47C1-BF82-05A179498811@me.com> (raw)
In-Reply-To: <C2452EA0-C85F-435E-BBEF-E1B3DCED6045@me.com>
Never mind - found it - https://sourceware.org/gdb/wiki/Internals%20Testsuite <https://sourceware.org/gdb/wiki/Internals%20Testsuite>
> On Jun 28, 2021, at 2:51 PM, Sam Warner <samuel.r.warner@me.com> wrote:
>
> Hi,
> One more newbie question. After building, is there a canned set of tests to make sure what I built matches what’s expected?
> (Using gcc-11 from home-brew)
>
> Sam
>
>
>> On Jun 27, 2021, at 5:48 PM, Simon Marchi <simon.marchi@polymtl.ca> wrote:
>>
>> On 2021-06-27 6:44 p.m., Sam Warner wrote:
>>> Hi Simon,
>>>
>>> Thanks - yes - I’ll start with that patch first. I obtain the same call stack
>>>
>>> My next two things to learn is how to get the equivalent of the symbol-server working, and then to setup a developer-environment for GDB. Any pointers would be great.
>>
>> I don't know what symbol-server is, I can't help you with that.
>>
>> To build gdb, you normally just need to run these commands at the
>> top-level:
>>
>> ./configure
>> make all-gdb
>>
>> The built gdb will be at gdb/gdb. But there are some additional quirks
>> on macOS though, so it's not as simple as that. GDB requires libgmp, so
>> you need to install that. You need GNU make to build (the make that
>> comes with macOS is not GNU make). You can install those using Macports
>> (or Brew, I guess) or by building them by hand. You can then probably
>> get by using the commands:
>>
>> ./configure --disable-nls CFLAGS="-g3 -O0" CXXFLAGS="-std=gnu++17 -g3 -O0" --with-libgmp-prefix=/opt/local
>> gmake
>>
>> Update /opt/local to point where your libgmp is installed. gmake refers
>> to GNU make, when installed through Macports.
>>
>> Simon
>
next prev parent reply other threads:[~2021-06-29 0:03 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 [this message]
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
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=810B4416-EE0C-47C1-BF82-05A179498811@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).