From: "Sherry Samuel" <SherryS@KPITCummins.com>
To: <cagney@gnu.org>
Cc: <gdb-patches@sources.redhat.com>
Subject: RE: [Patch H8/300] : Fix for crashing of gdb with" info f" command
Date: Fri, 09 Jul 2004 12:12:00 -0000 [thread overview]
Message-ID: <4A1BE23A7B777442B60F4B4916AE0F130218AAA5@sohm.kpit.com> (raw)
Hi
Reference:http://sources.redhat.com/ml/gdb-patches/2004-06/msg00428.html
In the latest GDB(gdb+dejagnu-20040630) snap shot, the "info f" problem described in the above link is fixed. Referring through the links you have suggested, it is evident that h8300 target is not in the list of the new GDB frame structure. Is it possible to know what should be done from our side to update H8300 targets to the new frame work? Can you suggest how to go about it?
Thanks in advance.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: Andrew Cagney [mailto:cagney@gnu.org]
Sent: Wednesday, June 23, 2004 1:39 AM
To: Sherry Samuel
Cc: gdb-patches@sources.redhat.com
Subject: Re: [Patch H8/300] : Fix for crashing of gdb with" info f"
command
> ******************CHANGELOG TEXT*******************************************************************
> 2004-06-18 Sherry Samuel <SherryS@KPITCummins.com>
>
> * h8300-tdep.c (h8300_frame_init_saved_regs) : Check whether frame base
> is null.
Are you sure this patch is against 6.1 or a current GDB? The function
h8300_frame_init_saved_regs has a void return type.
Also, you might want to read over:
Post GDB 6.2, require new frame code
http://sources.redhat.com/ml/gdb/2004-06/msg00199.html
As this will affect the h8/300.
Andrew
>
> --- 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);
next reply other threads:[~2004-07-09 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 12:12 Sherry Samuel [this message]
2004-07-15 18:18 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 10:35 Sherry Samuel
2004-06-22 20:09 ` 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=4A1BE23A7B777442B60F4B4916AE0F130218AAA5@sohm.kpit.com \
--to=sherrys@kpitcummins.com \
--cc=cagney@gnu.org \
--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