Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Debugging the C++ standard library on macOS (2022)

jviotti.com

Post reply on HN
Print view View original

11–20 of 20 posts

Re: Debugging the C++ standard library on macOS (2022)

#11

Post by saagarjha »

mistrial9 wrote: post #3
saagarjha wrote: post #2

Of course, LLDB is more likely than not to be useless when debugging complex templated code from the standard library :(

what is the constructive part of this comment? the debugger does what it is designed to do, and this author shows a clear example of setting it up? kudos to the clarity of this simple effort in the "tangled forests" that are Modern C++

I guess it's a warning to people who try to do this and find that the debugging experience may not be what they expected it to be. Nothing against the author, of course.

Re: Debugging the C++ standard library on macOS (2022)

#12

Post by account42 »

pipo234 wrote: post #10
bastawhiz wrote: post #6

Earlier quoted context omitted.

What part of this isn't about debugging the C++ stdlib on macOS? It talks about the special version of clang in Xcode. It has macOS-specific options. It gets into the details of doing this with Mach-O files. Almost no parts of this post isn't about the c++ stdlib and essentially all of it is specific to macOS.

I guess what chrisjj might have meant is that "debugging" usually starts with a bug, a or symptom. So in case of debugging the standard library, it usually is a problem in your own code that you cannot explain and try to blame on an error of the subsystem. In those cases, having access to a source-level debugger can be useful but in my experience this the subsystem is usually not where you'll find the error; more oft…

> but in my experience this the subsystem is usually not where you'll find the error; more often it's in your own code

More often perhaps, but compilers and their standard libraries are complex pieces of software written by human beings - and it's not that uncommon to encounter them, especially if you go a bit off the beaten path or are an early adopter.

Re: Debugging the C++ standard library on macOS (2022)

#13

Post by pipo234 »

account42 wrote: post #12
pipo234 wrote: post #10

Earlier quoted context omitted.

I guess what chrisjj might have meant is that "debugging" usually starts with a bug, a or symptom. So in case of debugging the standard library, it usually is a problem in your own code that you cannot explain and try to blame on an error of the subsystem. In those cases, having access to a source-level debugger can be useful but in my experience this the subsystem is usually not where you'll find the error; more oft…

> but in my experience this the subsystem is usually not where you'll find the error; more often it's in your own code More often perhaps, but compilers and their standard libraries are complex pieces of software written by human beings - and it's not that uncommon to encounter them, especially if you go a bit off the beaten path or are an early adopter.

Sure, that happens too. And it would be interesting to read an article about that; but that is not what this article is about despite its title :-)

Re: Debugging the C++ standard library on macOS (2022)

#14

Post by chrisjj »

bastawhiz wrote: post #6
chrisjj wrote: post #5

> Debugging the C++ standard library on macOS Some mistake. The article contains nothing on this subject.

What part of this isn't about debugging the C++ stdlib on macOS? It talks about the special version of clang in Xcode. It has macOS-specific options. It gets into the details of doing this with Mach-O files. Almost no parts of this post isn't about the c++ stdlib and essentially all of it is specific to macOS.

> Almost no parts of this post isn't about the c++ stdlib and essentially all of it is specific to macOS.

True. But notice the word Debugging is missing there.

Re: Debugging the C++ standard library on macOS (2022)

#15

Post by chrisjj »

vore wrote: post #7
chrisjj wrote: post #5

> Debugging the C++ standard library on macOS Some mistake. The article contains nothing on this subject.

I know Hacker News guidelines say you're not supposed to ask if someone's read the article but... did you even read the article? What part of the article is not about C++ and macOS?

> did you even read the article?

Yup. No offence taken.

> What part of the article is not about C++ and macOS?

None of it.

But what part /is/ about debugging that?

None of it.

Re: Debugging the C++ standard library on macOS (2022)

#16

Post by infamouscow »

chrisjj wrote: post #15
vore wrote: post #7

Earlier quoted context omitted.

I know Hacker News guidelines say you're not supposed to ask if someone's read the article but... did you even read the article? What part of the article is not about C++ and macOS?

> did you even read the article? Yup. No offence taken. > What part of the article is not about C++ and macOS? None of it. But what part /is/ about debugging that? None of it.

> Finally, we can break on insert_or_assign as expected and start exploring areas of interest within the standard library

Did you miss this part?

Re: Debugging the C++ standard library on macOS (2022)

#17

Post by chrisjj »

infamouscow wrote: post #16
chrisjj wrote: post #15

Earlier quoted context omitted.

> did you even read the article? Yup. No offence taken. > What part of the article is not about C++ and macOS? None of it. But what part /is/ about debugging that? None of it.

> Finally, we can break on insert_or_assign as expected and start exploring areas of interest within the standard library Did you miss this part?

Nope.

Debugging - the process of identifying and removing errors from computer hardware or software.

Re: Debugging the C++ standard library on macOS (2022)

#18

Post by infamouscow »

chrisjj wrote: post #17
infamouscow wrote: post #16

Earlier quoted context omitted.

> Finally, we can break on insert_or_assign as expected and start exploring areas of interest within the standard library Did you miss this part?

Nope. Debugging - the process of identifying and removing errors from computer hardware or software.

If you insist on being so pedantic, what makes you so sure the breakpoint isn't an error?

Re: Debugging the C++ standard library on macOS (2022)

#19

Post by jviotti »

Author here. Thanks for sharing! I have small collection of other Apple-related deep-dive articles that you might find interesting too, like:

- https://www.jviotti.com/2021/07/23/a-deep-dive-on-macos-univ...

- https://www.jviotti.com/2022/02/21/emitting-signposts-to-ins...

- https://www.jviotti.com/2022/11/28/launching-macos-applicati...

- https://www.jviotti.com/2022/02/24/attaching-lldb-to-product...

Re: Debugging the C++ standard library on macOS (2022)

#20

Post by chrisjj »

infamouscow wrote: post #18
chrisjj wrote: post #17

Earlier quoted context omitted.

Nope. Debugging - the process of identifying and removing errors from computer hardware or software.

If you insist on being so pedantic, what makes you so sure the breakpoint isn't an error?

Nothing. But that's immaterial, given the issue is the content of the article not the content of the code.

But what do think /is/ the meaning of "debugging" here, if not the common-usage one seen in the dictionary?

Post reply on HN