From: "Sherry Samuel" <SherryS@KPITCummins.com>
To: <gdb-patches@sources.redhat.com>
Subject: [Patch H8/300] : Fix for crashing of gdb with" info f" command
Date: Fri, 18 Jun 2004 10:35:00 -0000 [thread overview]
Message-ID: <4A1BE23A7B777442B60F4B4916AE0F1301AE175D@sohm.kpit.com> (raw)
Hi,
GDB6.1 for H8/300 targets crashes with "info f" command with a breakpoint in main.
**********************************************************************************************
Try the code below with h8300-elf toolchain
----------------Start of bug.c ---------------------
1 int main()
2 {
3 int i;
4
5 i=0;
6 }
----------------End of bug.c ------------------------
Compile with
h8300-elf-gcc bug.c -g
Load the a.out file produced into gdb simulator. Put a break point in line 2 of main and run gdb.
When the control reaches the breakpoint at main, try to get the frame information by the "info f"
command. The gdb crashes.
While just before entering main, the frame pointer register is not set. It contains 0x00. At this point
if we try to take the frame information by "info f" command the gdb crashes. After the frame pointer
register is set, gdb will not crash by the "info f" command.
This bug is not observed for gdb6.1 for SH targets.
**************************************************************************************************
Please find the patch below which fixes the same.
******************CHANGELOG TEXT*******************************************************************
2004-06-18 Sherry Samuel <SherryS@KPITCummins.com>
* h8300-tdep.c (h8300_frame_init_saved_regs) : Check whether frame base
is null.
***************************************************************************************************
--- gdb-6.1/gdb/h8300-tdep.c.old 2004-06-17 15:57:18.000000000 +0530
+++ gdb-6.1/gdb/h8300-tdep.c 2004-06-17 17:08:54.000000000 +0530
@@ -500,8 +500,8 @@ h8300_frame_init_saved_regs (struct fram
CORE_ADDR limit = (sal.end && sal.end < get_frame_pc (fi))
? sal.end : get_frame_pc (fi);
/* This will fill in fields in fi. */
-
-
+ if(!get_frame_base (fi))//check whether frame is null.
+ return null_frame_id;//if null return
h8300_examine_prologue (func_addr, limit, get_frame_base (fi),
deprecated_get_frame_saved_regs (fi), fi);
***************************************************************************************
Regards,
Sherry Samuel,
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 are released on June 1, 2004.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2004-06-18 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 10:35 Sherry Samuel [this message]
2004-06-22 20:09 ` Andrew Cagney
2004-07-09 12:12 Sherry Samuel
2004-07-15 18:18 ` Andrew Cagney
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=4A1BE23A7B777442B60F4B4916AE0F1301AE175D@sohm.kpit.com \
--to=sherrys@kpitcummins.com \
--cc=gdb-patches@sources.redhat.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