Title: Launching two configurations is fine, but launching just one would be waaay cooler. · Issue #6 · moosetechnology/JavaCallStackExtractor · GitHub
Open Graph Title: Launching two configurations is fine, but launching just one would be waaay cooler. · Issue #6 · moosetechnology/JavaCallStackExtractor
X Title: Launching two configurations is fine, but launching just one would be waaay cooler. · Issue #6 · moosetechnology/JavaCallStackExtractor
Description: Currently to extract a call stack you need to launch the program you want to analyze, then launch JavaCallStackExtractor, it is fine for a first approach, but having to launch only one would be better. *Proposal 1: Instantiate a VM progr...
Open Graph Description: Currently to extract a call stack you need to launch the program you want to analyze, then launch JavaCallStackExtractor, it is fine for a first approach, but having to launch only one would be bet...
X Description: Currently to extract a call stack you need to launch the program you want to analyze, then launch JavaCallStackExtractor, it is fine for a first approach, but having to launch only one would be bet...
Opengraph URL: https://github.com/moosetechnology/JavaCallStackExtractor/issues/6
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Launching two configurations is fine, but launching just one would be waaay cooler.","articleBody":"Currently to extract a call stack you need to launch the program you want to analyze, then launch JavaCallStackExtractor, it is fine for a first approach, but having to launch only one would be better.\n\n**Proposal 1: Instantiate a VM programatically*\nIt might be possible to instantiate our own VM with enough information about the used libraries and the location of the main method.\n\n**Proposal 2: Make this project a java agent**\nIt might be possible to transform this program in a java agent, this way it will be necessary to launch the program to analyze using a java agent argument like this on the VM : -javaagent:/path/to/*CSExtractor.jar*=*configFileName*","author":{"url":"https://github.com/LeoDefossez","@type":"Person","name":"LeoDefossez"},"datePublished":"2025-08-11T12:23:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/6/JavaCallStackExtractor/issues/6"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:17b55ce5-e64f-4fab-980a-8746b3bf044b |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | DD40:2DA0A8:48060B:617932:6969AFBC |
| html-safe-nonce | 69b1de44f4f79f06fbaf6fb5476419cdd62066ef204c5a96095a3c5ec6c93f8b |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJERDQwOjJEQTBBODo0ODA2MEI6NjE3OTMyOjY5NjlBRkJDIiwidmlzaXRvcl9pZCI6IjEwMjY4OTAwNjIwODc5MDQ2MCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | e8dfed49bfc0fbe40ccb9d47189f2c7d7a42ccd1144cbc9d1e793155b6e969a8 |
| hovercard-subject-tag | issue:3309801496 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/moosetechnology/JavaCallStackExtractor/6/issue_layout |
| twitter:image | https://opengraph.githubassets.com/ec84a3d39f497d4cbdbfe2687ead116c4ab6de23026b0f32c17a4059ed90324a/moosetechnology/JavaCallStackExtractor/issues/6 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/ec84a3d39f497d4cbdbfe2687ead116c4ab6de23026b0f32c17a4059ed90324a/moosetechnology/JavaCallStackExtractor/issues/6 |
| og:image:alt | Currently to extract a call stack you need to launch the program you want to analyze, then launch JavaCallStackExtractor, it is fine for a first approach, but having to launch only one would be bet... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | LeoDefossez |
| hostname | github.com |
| expected-hostname | github.com |
| None | b23b8fcc855cd29bb04d6c94aafa62d336bf44eefa8229444eecc968cad03aee |
| turbo-cache-control | no-preview |
| go-import | github.com/moosetechnology/JavaCallStackExtractor git https://github.com/moosetechnology/JavaCallStackExtractor.git |
| octolytics-dimension-user_id | 13623321 |
| octolytics-dimension-user_login | moosetechnology |
| octolytics-dimension-repository_id | 1013615922 |
| octolytics-dimension-repository_nwo | moosetechnology/JavaCallStackExtractor |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1013615922 |
| octolytics-dimension-repository_network_root_nwo | moosetechnology/JavaCallStackExtractor |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 0672399d88424758731ec07fe24509e23bb17fb5 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width