Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
GHC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
gershomb
GHC
Commits
bc066558
Commit
bc066558
authored
7 years ago
by
Ben Gamari
Browse files
Options
Downloads
Patches
Plain Diff
users-guide: Document -g flag
parent
8bf50d50
Loading
Loading
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/users_guide/debug-info.rst
+7
-6
7 additions, 6 deletions
docs/users_guide/debug-info.rst
with
7 additions
and
6 deletions
docs/users_guide/debug-info.rst
+
7
−
6
View file @
bc066558
...
...
@@ -5,13 +5,14 @@ Since the 7.10 release GHC can emit a debugging information to help debugging
tools understand the code that GHC produces. This debugging information is
useable by most UNIX debugging tools.
..
warning::
..
ghc-flag:: -g, -g<n>
This feature is still in technology preview state. There are known cases
where requesting a stack-trace can cause your program to segmentation fault
(e.g. :ghc-ticket:`11353`, :ghc-ticket:`11338`, and :ghc-ticket:`11337`).
Consequently, we can not recommend that stack trace support be used in
production code.
:since: 7.10, numeric levels since 8.0
Emit debug information in object code. Currently only DWARF debug
information is supported on x86-64 and i386. Currently debug levels 0
through 3 are accepted, with 0 disabling debug information production.
Levels 1 through 3 are functionally equivalent.
Tutorial
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment