* GDB crash problem on cygwin.
@ 2005-05-04 10:21 Nitin Shah
2005-05-04 10:41 ` Ramana Radhakrishnan
0 siblings, 1 reply; 4+ messages in thread
From: Nitin Shah @ 2005-05-04 10:21 UTC (permalink / raw)
To: gdb
Hi,
I have built gdb-6.3 on cygwin-1.5.9 for h8300 (coff and elf) target. I
tried to use command
(gdb) info frame, for h8300-elf target after putting breakpoint at main.
But it is crashing, although it works fine for h8300-coff target. I have
built the same gdb-6.3 on Linux, it works fine for both h8300-elf and
h8300-coff targets.
**************test_code.c**************************
int main()
{
int i=1;
i++;
return 0;
}
***************************************************
Command to compile:
h8300-elf-gcc test_code.c -g
Command to debug:
h8300-elf-gdb
(gdb) file a.out
(gdb) target sim
(gdb) load
(gdb) b 1
(gdb) r
(gdb) info frame
Here it crashes.
Kindly suggest how to solve this problem.
Thanks in advance.
Nitin Shah,
KPIT Cummins InfoSystems Ltd.
Pune, India
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Free download of GNU based tool-chains for Renesas' SH and H8 Series.
The following site also offers free technical support to its users.
Visit http://www.kpitgnutools.com for details.
Latest versions of KPIT GNU tools were released on February 4, 2005.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------
This message contains the information that may be privileged and is the property of the KPIT Cummins Infosystems LTD.It is intended only for the person to whom it is addressed. If you are not intended recipient, you are not authorized to read, print , retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Cummins does not accept any liability for virus infected mails.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: GDB crash problem on cygwin.
2005-05-04 10:21 GDB crash problem on cygwin Nitin Shah
@ 2005-05-04 10:41 ` Ramana Radhakrishnan
0 siblings, 0 replies; 4+ messages in thread
From: Ramana Radhakrishnan @ 2005-05-04 10:41 UTC (permalink / raw)
To: Nitin Shah; +Cc: gdb
Nitin Shah wrote:
> Hi,
> I have built gdb-6.3 on cygwin-1.5.9 for h8300 (coff and elf) target. I
> tried to use command
> (gdb) info frame, for h8300-elf target after putting breakpoint at main.
> But it is crashing, although it works fine for h8300-coff target. I have
> built the same gdb-6.3 on Linux, it works fine for both h8300-elf and
> h8300-coff targets.
>
> **************test_code.c**************************
> int main()
> {
> int i=1;
> i++;
> return 0;
> }
> ***************************************************
> Command to compile:
> h8300-elf-gcc test_code.c -g
>
> Command to debug:
> h8300-elf-gdb
> (gdb) file a.out
> (gdb) target sim
> (gdb) load
> (gdb) b 1
> (gdb) r
> (gdb) info frame
set debug frame 1 and send the output on the list. Maybe
someone can then see the error.
> Here it crashes.
What is the crash message ? Use the script command and send
that output on the list.
cheers
Ramana
--
Ramana Radhakrishnan
GNU Tools
codito ergo sum (www.codito.com)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: GDB crash problem on cygwin.
2005-05-04 13:06 Nitin Shah
@ 2005-05-05 12:56 ` Ramana Radhakrishnan
0 siblings, 0 replies; 4+ messages in thread
From: Ramana Radhakrishnan @ 2005-05-05 12:56 UTC (permalink / raw)
To: Nitin Shah; +Cc: gdb
Hi,
With today's cvs and your testcase, (again you haven't mentioned which
version of gcc and binutils you used to build it.) With whatever older
version of the h8 toolchain that I have , on cygwin I didn't get any
problems with the simulator. (from GCC CVS head in July / August 04 and
binutils head in the same period . )
info frame gave me correct frame info and the simulator did not crash.
One way for you to go forward would be to run gdb within gdb and see
exactly where it crashes, then maybe you can analyze it further.
HTH
cheers
Ramana
>
> Breakpoint 1, main () at test.c:2
>
> Regards,
> Nitin Shah
>
>
> -----Original Message-----
> From: Ramana Radhakrishnan [mailto:ramana.radhakrishnan@codito.com]
> Sent: Wednesday, May 04, 2005 4:11 PM
> To: Nitin Shah
> Cc: gdb@sources.redhat.com
> Subject: Re: GDB crash problem on cygwin.
>
> Nitin Shah wrote:
>
>>Hi,
>>I have built gdb-6.3 on cygwin-1.5.9 for h8300 (coff and elf) target.
>>I tried to use command
>>(gdb) info frame, for h8300-elf target after putting breakpoint at
>
> main.
>
>>But it is crashing, although it works fine for h8300-coff target. I
>>have built the same gdb-6.3 on Linux, it works fine for both h8300-elf
>
>
>>and h8300-coff targets.
>>
>>**************test_code.c**************************
>>int main()
>>{
>> int i=1;
>> i++;
>> return 0;
>>}
>>***************************************************
>>Command to compile:
>>h8300-elf-gcc test_code.c -g
>>
>>Command to debug:
>>h8300-elf-gdb
>>(gdb) file a.out
>>(gdb) target sim
>>(gdb) load
>>(gdb) b 1
>>(gdb) r
>>(gdb) info frame
>
>
> set debug frame 1 and send the output on the list. Maybe someone can
> then see the error.
>
>
>
>
>
>
>>Here it crashes.
>
>
> What is the crash message ? Use the script command and send
> that output on the list.
>
>
> cheers
> Ramana
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: GDB crash problem on cygwin.
@ 2005-05-04 13:06 Nitin Shah
2005-05-05 12:56 ` Ramana Radhakrishnan
0 siblings, 1 reply; 4+ messages in thread
From: Nitin Shah @ 2005-05-04 13:06 UTC (permalink / raw)
To: Ramana Radhakrishnan; +Cc: gdb
Hi,
After set debug frame 1, while running the run command I have log the
output mentioned below, after this if I give "info frame" command, it's
completely crashes and closed the complete gdb.
*************************gdb.txt****************************************
****
{ flush_cached_frames () }
{ frame_id_p (l={stack=0x0,code=0x0,special=0x0}) -> 0 }
{ frame_id_p (l={stack=0x0,code=0x0,special=0x0}) -> 0 }
{ frame_id_p (l={stack=0x0,code=0x0,special=0x0}) -> 0 }
{ frame_id_p (l={stack=0x0,code=0x0,special=0x0}) -> 0 }
{ create_sentinel_frame (...) ->
{level=-1,type=NORMAL_FRAME,unwind=0x52a2b4,pc=<unknown>,id={stack=0x0,c
ode=0x0,special=0x0},func=<unknown>} }
{ get_prev_frame (this_frame=-1) { frame_pc_unwind (this_frame=-1) ->
0x1a8 }
{ deprecated_update_frame_pc_hack (frame=0,pc=0x1a8) }
{ frame_id_p (l={stack=0x0,code=0x1a8,special=0x0}) -> 0 }
-> <NULL frame> // unwound legacy ID invalid }
{ deprecated_update_frame_pc_hack (frame=-1,pc=0x1a8) }
************************************************************************
****
Breakpoint 1, main () at test.c:2
Regards,
Nitin Shah
-----Original Message-----
From: Ramana Radhakrishnan [mailto:ramana.radhakrishnan@codito.com]
Sent: Wednesday, May 04, 2005 4:11 PM
To: Nitin Shah
Cc: gdb@sources.redhat.com
Subject: Re: GDB crash problem on cygwin.
Nitin Shah wrote:
> Hi,
> I have built gdb-6.3 on cygwin-1.5.9 for h8300 (coff and elf) target.
> I tried to use command
> (gdb) info frame, for h8300-elf target after putting breakpoint at
main.
> But it is crashing, although it works fine for h8300-coff target. I
> have built the same gdb-6.3 on Linux, it works fine for both h8300-elf
> and h8300-coff targets.
>
> **************test_code.c**************************
> int main()
> {
> int i=1;
> i++;
> return 0;
> }
> ***************************************************
> Command to compile:
> h8300-elf-gcc test_code.c -g
>
> Command to debug:
> h8300-elf-gdb
> (gdb) file a.out
> (gdb) target sim
> (gdb) load
> (gdb) b 1
> (gdb) r
> (gdb) info frame
set debug frame 1 and send the output on the list. Maybe someone can
then see the error.
> Here it crashes.
What is the crash message ? Use the script command and send
that output on the list.
cheers
Ramana
--
Ramana Radhakrishnan
GNU Tools
codito ergo sum (www.codito.com)
---------------------------------
This message contains the information that may be privileged and is the property of the KPIT Cummins Infosystems LTD.It is intended only for the person to whom it is addressed. If you are not intended recipient, you are not authorized to read, print , retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Cummins does not accept any liability for virus infected mails.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-05-05 12:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-05-04 10:21 GDB crash problem on cygwin Nitin Shah
2005-05-04 10:41 ` Ramana Radhakrishnan
2005-05-04 13:06 Nitin Shah
2005-05-05 12:56 ` Ramana Radhakrishnan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox