Insight crashes when I open a located image

Insight crashes when I open a located image

[Gerwyn Davies]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

Hello,
 
I have a problem where Insight crashes out 
when  I open an linked and located object file, and was hoping that someone 
may be able to shed some light onto it.
 
I'm using:-
>GNU gdb 
4.17-gnupro-98r2 >This GDB was configured as "--host=i586-pc-cygwin32 
--target=mips-tx39-elf".
I dont know what version of 
Insight I'm using, maybe someone could tell me how to find this 
out.
 
I've taken a look at the object file with objdump and can't 
see anything wrong with it. If I open a compiled object, Insight is happy. I 
know what you're going to say:- "Try it with GDB 5.0!", but I only 
want to use GDB 5.0 if I have to.
 
 
Many thanks.
 
Gerwyn
 
 

Insight crashes when I open a located image

[Gerwyn Davies]

(No HTML this time I hope!)

Hello,

I have a problem where Insight crashes out when  I open an linked and
located object file, and was hoping that someone may be able to shed some
light onto it.

I'm using:-
>GNU gdb 4.17-gnupro-98r2
>This GDB was configured as
"--host=i586-pc-cygwin32 --target=mips-tx39-elf".
I dont know what version of Insight I'm using, maybe someone could tell me
how to find this out.

I've taken a look at the object file with objdump and can't see anything
wrong with it. If I open a compiled object, Insight is happy. I know what
you're going to say:- "Try it with GDB 5.0!", but I only want to use GDB 5.0
if I have to.


Many thanks.

Gerwyn

Re: Insight crashes when I open a located image

[Fernando Nasser]

Gerwyn Davies wrote:
> 
> I've tried using gdb -nw, but I have a very hard time trying to connect to
> the target. Here's a trace:-
> 
> >Remote debugging using com1
> >Sending packet: $Hc-1#09...putpkt: Junk:
> 
> Nothing will happen, until I press the NMI button, then on rare occaisions I
> can connect. I don't have this problem when using Insight, but I do still
> have to press the NMI once before I can connect to the board.
> 
The diference is that Insight (the GUI) always send a "set remotebaud NNNN" before
the "Target" command.

Please try the sequence:

set remotebaud 9600     (or whatever your board speed is)
target remote com1      (I am assuming your board monitor has a gdb remote stub, 'course)

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299
From kings@ms29.url.com.tw Fri Jul 21 11:38:00 2000
From: "kings" <kings@ms29.url.com.tw>
To: <gdb@sourceware.cygnus.com>
Subject: an error in gdb insight
Date: Fri, 21 Jul 2000 11:38:00 -0000
Message-id: <000f01bed3a6$c9e65560$4e6119a3@vlsi>
X-SW-Source: 2000-07/msg00079.html
Content-length: 402

Dear maintainer:

when i run my program in console window. There is an error message.

starting program: /usr4/student/kings/mchang/testv2 12 34 56 78 90
Error: procfs: target_wait (wait_for_stop) line 3677,
/proc/05589:Interrupted system call.

my computer is sparc-sun-solaris with X11R5 and gdb -v is gdb 20000423

Does it matter? What should i do?

PS: If i use gdb -nw. everything work normally.