Re: gdb says: internal-error...
Re: gdb says: internal-error...
- Subject: Re: gdb says: internal-error...
- From: Jim Ingham <email@hidden>
- Date: Thu, 20 Jul 2006 11:05:38 -0700
This is a known bug. I've fixed it already, so the fix will be out
whenever our next release comes.
The problem is that the first time we go to evaluate a variable's
value we get some kind of error, usually the variable isn't in scope
yet. I wasn't handling the error correctly in some corner cases. You
can sometimes work around the error by breaking a little further on in
the function that was causing problems. Then on first evaluation the
variable will be valid, and you can sidestep the bug.
Jim
On Jul 20, 2006, at 5:23 AM, Andreas Tuerk wrote:
Hi Kurt,
I had the same problem when I was trying to debug a C (not C++)
program that I had built with various makefiles outside Xcode. This
was the result of an incorrect set of compile options. I could solve
the problem in two different ways:
1. rebuild the program inside Xcode, which means throwing away the
makefiles and creating an Xcode project containing all the source
files, dependencies, etc. that were previously defined in the
makefiles.
2. change the makefiles: for this you need to look at the output of
the build results of the Xcode project of point 1 and add compiler
options such as: -x c -arch i386 -pipe -Wno-trigrap
hs -fpascal-strings -fasm-blocks -O0 -fmessage-length=0 -mfix-and-
continue
You will also need to use libtool rather than ar to archive any
object files into a static library.
If you are not using makefiles but instead an Xcode project that you
have been developing under Xcode 2.2 I suggest you try building a
new project inside Xcode 2.3 with exactly the same source files,
dependencies, etc. as this should set the compiler options correctly.
Hope this helps,
Andreas
below follows the original message <<<<<<<<<<<<<<
I have recently upgraded to 2.3, and at first everything went fine.
I was happily debugging our Carbon C++ project using DWARF debug
information.
Now, after some days, debugging stopped working. Whenever I run into
a breakpoint, gdb tells me:
/SourceCache/gdb/gdb-477/src/gdb/varobj.c:2007: internal-error:
my_value_equal: Assertion `!value_lazy (val1)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
And then it stops.
Clearing all breakpoints, cleaning all targets and rebuilding them
does not help. I honestly have no clue as to where I should start
trying to fix this.
Any advice is appreciated.
Kurt
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden