{"action":"opened","issue":{"url":"https://api.github.com/repos/maven-nar/nar-maven-plugin/issues/244","repository_url":"https://api.github.com/repos/maven-nar/nar-maven-plugin","labels_url":"https://api.github.com/repos/maven-nar/nar-maven-plugin/issues/244/labels{/name}","comments_url":"https://api.github.com/repos/maven-nar/nar-maven-plugin/issues/244/comments","events_url":"https://api.github.com/repos/maven-nar/nar-maven-plugin/issues/244/events","html_url":"https://github.com/maven-nar/nar-maven-plugin/issues/244","id":172994504,"number":244,"title":"option of full path to filenames added for gcc builds","user":{"login":"manu4linux","id":15072540,"avatar_url":"https://avatars.githubusercontent.com/u/15072540?v=3","gravatar_id":"","url":"https://api.github.com/users/manu4linux","html_url":"https://github.com/manu4linux","followers_url":"https://api.github.com/users/manu4linux/followers","following_url":"https://api.github.com/users/manu4linux/following{/other_user}","gists_url":"https://api.github.com/users/manu4linux/gists{/gist_id}","starred_url":"https://api.github.com/users/manu4linux/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/manu4linux/subscriptions","organizations_url":"https://api.github.com/users/manu4linux/orgs","repos_url":"https://api.github.com/users/manu4linux/repos","events_url":"https://api.github.com/users/manu4linux/events{/privacy}","received_events_url":"https://api.github.com/users/manu4linux/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-24T16:08:06Z","updated_at":"2016-08-24T16:08:06Z","closed_at":null,"body":"we see that all the debug string filenames with in executable now only have relative path to main. for example `/base/project/src/main/c/somefile.c` would show as `c/somefile.c`\r\nSince our project use a static dependency libs, let say file from `/base/project2/src/main/c/someotherfile.c` will resolve to `c/someotherfile.c` causing GDB debugging issues. \r\n\r\nWe have 14 million lines of code spread out all over the place. Our build agents end up with paths like this:\r\n```\r\n/usr/local/teamcity/buildagent/work/41ae010f80e2cbba/cs_timer/src/main/c/cs_timer.c, \r\n/usr/local/teamcity/buildagent/work/41ae010f80e2cbba/cs_sequence/src/main/c/cs_sequence.c\r\n```\r\nIn our .gdbinit file, we can map `/usr/local/teamcity/buildagent/work/41ae010f80e2cbba/` to the top level of our source (as in `set substitute-path /usr/local/teamcity/buildagent/work/41ae010f80e2cbba/ /home/user/server/modules/c-libs`) and gdb can find the sources. But, without the full path and just `c/cs_env.c` or `c/cs_super.c` we’d have to have individual mapping for each file. That’s unworkable for us.\r\n\r\nif I am not wrong Behavior in old `maven-nar-plugin`  seem to give full path which made it easy for GDB to find them.\r\n\r\nFYI, pls see https://groups.google.com/forum/#!topic/maven-nar/sIBkEOdjDfA"}}
{"actor":{"display_login":"manu4linux"}}