This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: New feature "source-id"
- From: Doug Evans <dje at google dot com>
- To: Bruce Dawson <bruced at valvesoftware dot com>
- Cc: Gerhard Gappmeier <gerhard dot gappmeier at ascolab dot com>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 18 Mar 2014 10:57:39 -0700
- Subject: Re: New feature "source-id"
- Authentication-results: sourceware.org; auth=none
- References: <7365721 dot BnaR1nHazz at lt-gergap> <10414444 dot 6eOdp1cvY6 at ws-gergap> <CACTLOFqU9nyQqvc43LnGdULMg+WLxhJ-6O+neUT-DPNezqO5uA at mail dot gmail dot com> <2739108 dot yJ4Vgng9gv at ws-gergap> <CADPb22ShBWC=VSSiyWzNcb++tZwCKaNidKqb74gbmNn3W839sQ at mail dot gmail dot com> <2AC155A009400B4C8B05D518E4819AEF1A347889 at exchange10 dot valvesoftware dot com> <CADPb22QJ7bQdn+0hHYLw_f-wkTOzjFykBHuHRf9DKOrPDu1OrA at mail dot gmail dot com> <2AC155A009400B4C8B05D518E4819AEF1A347F4C at exchange10 dot valvesoftware dot com>
On Tue, Mar 18, 2014 at 10:44 AM, Bruce Dawson <bruced@valvesoftware.com> wrote:
> I better understand what you are doing now with the .c file now. Previously I had assumed that you would be compiling it and then linking the .o file along with all of the others.
>
> Now I am confused about *why* you are compiling it. If you have a text file that has the source information then why not just add it as a custom section directly? What is the value in compiling it into a .o file first?
More control over how the data can appear in the resulting section.
It's hardly an issue worth quibbling over.
I will leave it to the app developer / whatever to decide how best to
accomplish this.
The high order bit for me for the task at hand is that gdb doesn't need to care.