This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug macros/13205] New: Add support for __FILE__, __LINE__.


http://sourceware.org/bugzilla/show_bug.cgi?id=13205

             Bug #: 13205
           Summary: Add support for __FILE__, __LINE__.
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: macros
        AssignedTo: unassigned@sourceware.org
        ReportedBy: dje@google.com
    Classification: Unclassified


This is related to 9748, but concerns the specific cases of __FILE__, __LINE__.
[And maybe __FUNCTION__, __func__, __PRETTY_FUNCTION__ (though for reference
sake these aren't preprocessor macros).]

IWBN if the expression parser recognized these symbols and did the right thing.
As for producing the same value as GCC would in the presence of optimized code,
one has to weigh having cut-n-pasted expressions break versus producing some
answer.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]