From: Jimmy Guo <guo@cup.hp.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH] gdbarch.sh gdbarch.c
Date: Wed, 02 Aug 2000 15:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10008021518060.13046-100000@hpcll168.cup.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10007282035030.10690-100000@hpcll168.cup.hp.com>
FYI I've comitted this.
- Jimmy
On Fri, 28 Jul 2000, Jimmy Guo wrote:
>On Sat, 29 Jul 2000, Andrew Cagney wrote:
>
>>Jimmy Guo wrote:
>>>
>>> This patch is to prevent sizeof.exp 'maint print arch' to trigger
>>> gdb_internal_error (). inferior.h defines default to be the
>>> gdb_internal_error () call.
>>
>>Hmm, this needs some tinkering with gdbarch.sh :-(
>>
>> Andrew
>
>OK, here is the complete deal: gdbarch.sh and gdbarch.c:
>
>Fri Jul 28 20:35:27 Jimmy Guo <guo@cup.hp.com>
>
> * gdbarch.sh: Add print_p field for CALL_DUMMY_BREAKPINT_OFFSET
> to be printed only if CALL_DUMMY_BREAKPOINT_OFFSET_P.
>
> * gdbarch.c: Regenerated.
>
>Index: gdbarch.sh
>/usr/local/bin/diff -c -L gdbarch.sh gdbarch.sh@@/GDB_2000_07_24 gdbarch.sh
>*** gdbarch.sh
>--- gdbarch.sh Fri Jul 28 20:33:01 2000
>***************
>*** 314,320 ****
> v:2:CALL_DUMMY_LOCATION:int:call_dummy_location::::0:0
> f:2:CALL_DUMMY_ADDRESS:CORE_ADDR:call_dummy_address:void:::0:0::gdbarch->call_dummy_location == AT_ENTRY_POINT && gdbarch->call_dummy_address == 0
> v:2:CALL_DUMMY_START_OFFSET:CORE_ADDR:call_dummy_start_offset::::0:-1:::0x%08lx
>! v:2:CALL_DUMMY_BREAKPOINT_OFFSET:CORE_ADDR:call_dummy_breakpoint_offset::::0:-1:::0x%08lx
> v:1:CALL_DUMMY_BREAKPOINT_OFFSET_P:int:call_dummy_breakpoint_offset_p::::0:-1
> v:2:CALL_DUMMY_LENGTH:int:call_dummy_length::::0:-1:::::CALL_DUMMY_LOCATION == BEFORE_TEXT_END || CALL_DUMMY_LOCATION == AFTER_TEXT_END
> f:2:PC_IN_CALL_DUMMY:int:pc_in_call_dummy:CORE_ADDR pc, CORE_ADDR sp, CORE_ADDR frame_address:pc, sp, frame_address::0:0
>--- 314,320 ----
> v:2:CALL_DUMMY_LOCATION:int:call_dummy_location::::0:0
> f:2:CALL_DUMMY_ADDRESS:CORE_ADDR:call_dummy_address:void:::0:0::gdbarch->call_dummy_location == AT_ENTRY_POINT && gdbarch->call_dummy_address == 0
> v:2:CALL_DUMMY_START_OFFSET:CORE_ADDR:call_dummy_start_offset::::0:-1:::0x%08lx
>! v:2:CALL_DUMMY_BREAKPOINT_OFFSET:CORE_ADDR:call_dummy_breakpoint_offset::::0:-1:::0x%08lx::CALL_DUMMY_BREAKPOINT_OFFSET_P
> v:1:CALL_DUMMY_BREAKPOINT_OFFSET_P:int:call_dummy_breakpoint_offset_p::::0:-1
> v:2:CALL_DUMMY_LENGTH:int:call_dummy_length::::0:-1:::::CALL_DUMMY_LOCATION == BEFORE_TEXT_END || CALL_DUMMY_LOCATION == AFTER_TEXT_END
> f:2:PC_IN_CALL_DUMMY:int:pc_in_call_dummy:CORE_ADDR pc, CORE_ADDR sp, CORE_ADDR frame_address:pc, sp, frame_address::0:0
>Index: gdbarch.c
>/usr/local/bin/diff -c -L gdbarch.c gdbarch.c@@/GDB_2000_07_24 gdbarch.c
>*** gdbarch.c
>--- gdbarch.c Fri Jul 28 20:33:37 2000
>***************
>*** 1456,1464 ****
> (long) CALL_DUMMY_START_OFFSET);
> #endif
> #ifdef CALL_DUMMY_BREAKPOINT_OFFSET
>! fprintf_unfiltered (file,
>! "gdbarch_dump: CALL_DUMMY_BREAKPOINT_OFFSET = 0x%08lx\n",
>! (long) CALL_DUMMY_BREAKPOINT_OFFSET);
> #endif
> #ifdef CALL_DUMMY_BREAKPOINT_OFFSET_P
> fprintf_unfiltered (file,
>--- 1456,1465 ----
> (long) CALL_DUMMY_START_OFFSET);
> #endif
> #ifdef CALL_DUMMY_BREAKPOINT_OFFSET
>! if (CALL_DUMMY_BREAKPOINT_OFFSET_P)
>! fprintf_unfiltered (file,
>! "gdbarch_dump: CALL_DUMMY_BREAKPOINT_OFFSET = 0x%08lx\n",
>! (long) CALL_DUMMY_BREAKPOINT_OFFSET);
> #endif
> #ifdef CALL_DUMMY_BREAKPOINT_OFFSET_P
> fprintf_unfiltered (file,
prev parent reply other threads:[~2000-08-02 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10007282035030.10690-100000@hpcll168.cup.hp.com>
2000-07-28 20:59 ` Andrew Cagney
2000-08-02 15:19 ` Jimmy Guo [this message]
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=Pine.LNX.4.10.10008021518060.13046-100000@hpcll168.cup.hp.com \
--to=guo@cup.hp.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.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