From: "Nitin Shah" <NitinS2@KPITCummins.com>
To: "Ramana Radhakrishnan" <ramana.radhakrishnan@codito.com>
Cc: <gdb@sources.redhat.com>
Subject: RE: GDB crash problem on cygwin.
Date: Wed, 04 May 2005 13:06:00 -0000 [thread overview]
Message-ID: <4A1BE23A7B777442B60F4B4916AE0F1305627CF5@sohm.kpit.com> (raw)
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.
next reply other threads:[~2005-05-04 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 13:06 Nitin Shah [this message]
2005-05-05 12:56 ` Ramana Radhakrishnan
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 10:21 Nitin Shah
2005-05-04 10:41 ` Ramana Radhakrishnan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A1BE23A7B777442B60F4B4916AE0F1305627CF5@sohm.kpit.com \
--to=nitins2@kpitcummins.com \
--cc=gdb@sources.redhat.com \
--cc=ramana.radhakrishnan@codito.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox