Re: in search of squiggles
Project / Subsystem
gcc / gcc
Date
2026-07-28
Proposer
James K. Lowden <jklowden@cobolworx.com>
Source type
public_inbox
Consensus
Committed
Sentiment
—/10
Technical tradeoffs
- • Using verbose debugging options like -fdump-internal-locations can generate large amounts of output, potentially impacting build times and disk usage.
All attributes
- project
- gcc
- subsystem
- gcc
- patch_id
- —
- discussion_id
- 20260728161449.c71c09ccacbaf2c8c77cd2e5@cobolworx.com
- source_type
- public_inbox
- title
- Re: in search of squiggles
- headline
- Debugging internal compiler locations
- tldr
- User confirms -fdump-internal-locations helped debug a scanner location difference.
- proposer
- James K. Lowden <jklowden@cobolworx.com>
- consensus
- Committed
- outcome
- committed
- sentiment_score
- —
- technical_tradeoffs
-
- • Using verbose debugging options like -fdump-internal-locations can generate large amounts of output, potentially impacting build times and disk usage.
- series_id
- —
- series_role
- reply
- series_parts
- []
- tags
-
- • debugging
- • compiler internals
- • locations
- bugzilla_url
- —
- date
- 2026-07-28T00:00:00.000Z
Re: in search of squiggles
The user received assistance with a debugging issue related to scanner locations. The option -fdump-internal-locations proved instrumental in identifying a difference in reported locations between two branches, which was subsequently fixed.