[SERVER-13360] MongoDB will not build w/ CPU profiler enabled Created: 08/Oct/12 Updated: 19/Sep/15 Resolved: 11/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 3.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mongo Phan | Assignee: | Jonathan Reams |
| Resolution: | Done | Votes: | 0 |
| Labels: | build-jbr | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux / Debian |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | Linux | ||||||||
| Sprint: | BUILD 3 05/15/15 | ||||||||
| Participants: | |||||||||
| Description |
|
Use of the --cpu-profiler option will not build; gets a link error. Once built, I find the output from Google perftools pretty useless, e.g. most of the time is spontaneous calls to "memcpy" on a simple bulk-insert intensive script. Is anyone at all using the CPU profiler feature? Looks like not. |
| Comments |
| Comment by Githook User [ 11/May/15 ] | ||||||||||||||||||||||||
|
Author: {u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}Message: | ||||||||||||||||||||||||
| Comment by Ernie Hershey [ 24/Jul/14 ] | ||||||||||||||||||||||||
|
This command line gives one error:
And this command line gives this error:
| ||||||||||||||||||||||||
| Comment by Ernie Hershey [ 09/Jul/14 ] | ||||||||||||||||||||||||
|
I get errors in osx -
| ||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 06/Jun/14 ] | ||||||||||||||||||||||||
|
Hi mongophan, we haven't heard from you in a while. Are you still interested in pursuing this issue? Please let us know. Regards, | ||||||||||||||||||||||||
| Comment by Ernie Hershey [ 28/Apr/14 ] | ||||||||||||||||||||||||
|
hi mongophan, thanks for submitting this patch. It no longer cleanly applies in master though. Can you try with a more recent version of our source code and include the error you're seeing along with a new patch if you choose to update it? Also for us to consider a contribution you'll have to sign our contributors agreement here - http://www.mongodb.com/legal/contributor-agreement | ||||||||||||||||||||||||
| Comment by Randall Hunt [ 26/Oct/12 ] | ||||||||||||||||||||||||
|
schwerin this patch LGTM should we merge it? |