This is the mail archive of the insight@sources.redhat.com mailing list for the Insight 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]

Re: 5.3 problems on RH7.2


On Fri, 2003-08-01 at 01:39, Evan Lavelle wrote:
> This is on RH7.2, with gcc 3.3. I had the same issues with gcc 2.95. 
> These are large-ish static executables (10-15MB), linked against 
> pthreads and gtk 1.2, although the crashing code is actually 
> single-threaded and doesn't use gtk. I've done a sanity check against 
> ddd using the version of gdb in insight's bin directory, and it doesn't 
> have these problems (although it does have lots of its own problems, of 
> course).

First things first: I would recommend trying a newer version of Insight
-- especially if you're using gcc 3.3 and threads on linux. Although it
is unlikely that you will be running the newest threading model (NPTL),
if you are, the older gdb will not work at all.

> 1) I occasionally get an "Error: Can't read '_twin': no such variable" 
> message. Insight crashes at this point, and has to be killed. I got a 
> lot of these when debugging multi-threaded code (basically, I have to 
> use ddd for multi-threaded), but I still get it even when there's only 
> one thread.

I believe that this has been fixed. I don't know where or remember what
it was, though.

> 2) I quite frequently get an "Error: bad text index '4'" message when 
> opening a new source file. I can normally ignore this, although it does 
> seem that Insight occasionally crashes some time afterwards.

I think this has been mitigated. It may still occur, but I don't see it
very often. If you do see it with 6.0, I would appreciate a test case.

> 3) Stack  tracing frequently doesn't work, particularly if you're 
> debugging a core dump. The trace window doesn't show all the stack 
> levels, and clicking on a given level takes you to the wrong level.

Most likely a gdb probelm, as you indicate. When this happens, open a
console window and type "bt". Does that work? If it does, it's an
insight problem. If it doesn't, then it's a gdb problem.

Unless there is a real need to stick to 5.3, I encourage you to update
to 6.0 (unofficial), which is due for release sometime soon. You can
grab it by checking out the gdb_6_0-branch of insight.

Keith



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