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]

Re: Warning: Couldn't restore frame in current thread


The messages requested are:

$ gcc -v
Reading specs from /bin/../lib/gcc-lib/i686-pc-cygwin/2.95.3-4/specs
gcc version 2.95.3-4 (cygwin special)

$ uname -a
CYGWIN_98-4.10 A7W7R0 1.3.1(0.38/3/2) 2001-04-24 20:01 i586 unknown

My insight history is:

downloaded sources insight-5_0_tar.bz2 at 07/23/00
compiled with CYGWIN version actual at that time out of the box,
running configure, make, make install: absolutely no problems!

upgraded CYGWIN form time to time, also including gdb, by setup.exe, only
binaries. Actual gdb: gdb-20001125-1.tar. Warning message appeared around that
time ?!

Removed the old insight installation from /usr/local: still warning message.

Recompiled the July sources with CC='gcc -mwin32' configure, moved only gdb.exe to
/bin: gdb -nw is o.k., gdb exits without displaying any window.

Is the email from Fernando Nasser directly related to my problem? Where could I
find the actual sources to apply this patch?

Holger




Keith Seitz schrieb:

> On Wed, 2 May 2001, Holger Vogt wrote:
>
> > gdb -nw is working without problems.
> >
> > In Insight either typing n, s, si to the console window or mouse-clicking to
> > the source window will generate the warning message. It appears for the
> > first time  after typing 'run' to the console window.
>
> Wow, that is weird. The warning message you are displaying comes from gdb.
> I would not expect Insight to show this message at all. Something fishy
> must be going on...
>
> What does gdb -v show? (If you're on cygwin, can you include the output of
> "gcc -v" and "uname -a", too?)
>
> Keith


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