This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/14999] New: Clang debug info crashes GDB when trying tocollect local variables in a trace
- From: "dblaikie at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 07 Jan 2013 01:50:34 +0000
- Subject: [Bug c++/14999] New: Clang debug info crashes GDB when trying tocollect local variables in a trace
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14999
Bug #: 14999
Summary: Clang debug info crashes GDB when trying to collect
local variables in a trace
Product: gdb
Version: 7.5
Status: NEW
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned@sourceware.org
ReportedBy: dblaikie@gmail.com
Classification: Unclassified
Using Clang ToT (I believe this would easily reproduce with the recently
released 3.2 as well, perhaps with older versions too) to compile the following
program:
int func(int p) {
int x = p + 3;
return x;
}
int main() { return func(3); }
Then loading that into GDB (7.5) & executing the following:
trace 3
actions
collect x
end
At the "collect" point (reproduces when using "collect q" instead) GDB has the
following error:
../../gdb-7.5.x/gdb/tracepoint.c:665: internal-error: expression has min
height < 0
A problem internal to GDB has been detected,
further debugging may prove unreliable.
It'd be nice if GDB didn't fail. Beyond that, there's nothing in Clang's debug
info that seems unreasonable for this, but evidently there's /some/ difference
between GCC 4.7 and Clang's output here because GCC's output works just fine.
Perhaps the location information is broken in some way. (advice on that would
be appreciated, though not required - this bug is merely about the internal
error)
--
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.