/go

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/link: move symtab out of mapped memory #5914

Open
rsc opened this Issue Jul 18, 2013 · 5 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
  Unplanned
2 participants
@rsc @robpike
@rsc
Contributor

rsc commented Jul 18, 2013 

Nothing in package runtime looks at the Go 'symtab' symbol anymore. Move it into
unmapped memory, so that it is still in the file for debuggers but not mapped while the
program runs.

Low priority, since the size of the file will not be changing, and since the data is
never paged in, the total memory cost is under two pages of memory partially used by
fragmentation, so less than 8 kB.
@rsc

This comment has been minimized.

Sign in to view
Contributor

rsc commented Jul 30, 2013

Comment 1:

Labels changed: added go1.3, removed go1.2maybe.
@robpike

This comment has been minimized.

Sign in to view
Contributor

robpike commented Aug 20, 2013

Comment 2:

Labels changed: removed go1.3.
@rsc

This comment has been minimized.

Sign in to view
Contributor

rsc commented Nov 27, 2013

Comment 3:

Labels changed: added go1.3maybe.
@rsc

This comment has been minimized.

Sign in to view
Contributor

rsc commented Dec 4, 2013

Comment 4:

Labels changed: added release-none, removed go1.3maybe.
@rsc

This comment has been minimized.

Sign in to view
Contributor

rsc commented Dec 4, 2013

Comment 5:

Labels changed: added repo-main.

@rsc rsc added accepted labels Dec 4, 2013

@rsc rsc added this to the Unplanned milestone Apr 10, 2015

@rsc rsc removed priority-later labels Apr 10, 2015

@rsc rsc changed the title from cmd/ld: move symtab out of mapped memory to cmd/link: move symtab out of mapped memory Jun 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment