Explain C++ Inline, Segfaults, Virtual Memory, and std::string Internals
Company: Hudson River Trading
Role: Software Engineer
Category: Software Engineering Fundamentals
Difficulty: hard
Interview Round: Technical Screen
Answer a C++ systems interview covering inline functions and inline variables, segmentation faults, MMU address translation, TLB and page tables, page faults and traps, swap behavior, and how `std::string` is commonly implemented.
### Constraints & Assumptions
- Focus on conceptual correctness rather than one compiler implementation.
- C++ standard library internals can vary.
- Discuss common implementations and trade-offs.
- Use OS-level terminology precisely.
### Clarifying Questions to Ask
- Is the interviewer asking about language semantics or compiler optimization for inline?
- Should virtual memory be explained for Linux specifically?
- Do we need to cover copy-on-write or only paging?
- Should `std::string` include small-string optimization?
### What a Strong Answer Covers
```premium-lock What a Strong Answer Covers
```
### Follow-up Questions
- What happens when memory is allocated but not touched?
- How does swapping differ from demand paging?
- Why can inline increase binary size?
- How would you debug a segfault in production?
Quick Answer: This Hudson River Trading software engineering question probes C++ fundamentals, virtual memory, segmentation faults, inline functions, and std::string internals. It prepares candidates for low-level interviews that expect precise explanations of runtime behavior and performance trade-offs.