public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "keller at metrolab dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26949] ELF target support seems broken on macOS 11 Date: Mon, 22 Feb 2021 18:47:58 +0000 [thread overview] Message-ID: <bug-26949-4717-CuGry0Z8ND@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26949-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26949 --- Comment #11 from Philip Keller <keller at metrolab dot com> --- It's been many years since I really used gdb on Mac, always as a cross-debugger of course. Now I'm starting a new project, cross-compiling/debugging to embedded Linux (Yocto). I just got done setting up my development environment; gdb worked fine on Hello World & similar, but it did hang on a more complex test project. I haven't chased that one down yet; the project has a very complex object structure with multiple threads, console & network I/O, ... - many nooks & crannies that could fail. If gdb compiles, I don't see why it should be badly behaved on macOS. My experience is that (1) the clang compiler catches errors that gcc does not (and vice versa); and (2) macOS is missing some common libraries (e.g. internationalization). That second issue is usually easily remedied, for example with the MacPorts package manager. A native Mac development environment is worth something to me, so I intend to give it a good try, and I'd be happy to share what I find. However, I do have real work to do, so if it gets too much of a bother, I'll switch back to using a Linux VM development environment. Did that answer your question? Should I bother reporting back? If so, how? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-22 18:47 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-26 10:00 [Bug gdb/26949] New: " eblot.ml at gmail dot com 2020-11-26 13:15 ` [Bug gdb/26949] " eblot.ml at gmail dot com 2020-11-27 23:29 ` wilson at gcc dot gnu.org 2021-01-05 11:17 ` big_deady2 at web dot de 2021-01-05 16:00 ` simark at simark dot ca 2021-01-06 11:10 ` eblot.ml at gmail dot com 2021-02-09 1:54 ` sify21 at 163 dot com 2021-02-18 13:59 ` keller at metrolab dot com 2021-02-18 15:35 ` simark at simark dot ca 2021-02-22 12:46 ` keller at metrolab dot com 2021-02-22 16:40 ` simark at simark dot ca 2021-02-22 18:20 ` eblot.ml at gmail dot com 2021-02-22 18:47 ` keller at metrolab dot com [this message] 2021-02-22 18:48 ` keller at metrolab dot com 2021-02-22 20:03 ` simark at simark dot ca 2021-02-22 22:21 ` keller at metrolab dot com 2021-02-23 1:42 ` simark at simark dot ca 2021-02-23 7:17 ` keller at metrolab dot com
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=bug-26949-4717-CuGry0Z8ND@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).