From: "Denis Joseph Barrow" <DJBARROW@de.ibm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: gdb & gdbserver for s390 31 & 64 bit
Date: Thu, 27 Sep 2001 04:00:00 -0000 [thread overview]
Message-ID: <OF797DFD92.6C4D6303-ONC1256AD4.003B136C@de.ibm.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Hi Andrew,
>I need to think about both gdbarch.sh and tm-sysv4.h. Denis, can you
>expand?
The tm-sysv4.h patch was simply needed to get the stuff to compile
multiarch,
I don't think most/all other stuff which uses tm-sysv4.h are compiled
multiarch which is
why I don't think you've seen this before.
The SKIP_TRAMPOLINE_CODE macro is also defined in gdbarch.h.
The multiarch CALL_DUMMY_BREAKPOINT_OFFSET function that was emitted by
the old gdbarch.sh didn't check CALL_DUMMY_BREAKPOINT_OFFSET_P to see
that there was no multiarch version of this function available, therefore
my code failed the runtime check on startup without this fix.
I do a set_gdbarch_call_dummy_breakpoint_offset_p(gdbarch,0); to indidcate
that we don't have a CALL_DUMMY_BREAKPOINT_OFFSET function for s390 in
tm-s390.c
I believe/hope that was the intention of the CALL_DUMMY_BREAKPOINT_OFFSET_P
macro.
Hope this clears things up :-).
D.J. Barrow Gnu/Linux for S/390 kernel developer
eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
Phone: +49-(0)7031-16-2583
IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen
next reply other threads:[~2001-09-27 4:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 4:00 Denis Joseph Barrow [this message]
2001-09-27 18:40 ` Andrew Cagney
2001-09-27 20:17 ` Andrew Cagney
2001-09-27 20:29 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2001-10-01 4:49 Denis Joseph Barrow
2001-10-01 8:44 ` Andrew Cagney
2001-09-28 4:38 Denis Joseph Barrow
2001-09-28 10:33 ` Andrew Cagney
2001-09-10 11:55 Denis Joseph Barrow
2001-09-26 17:37 ` Andrew Cagney
2001-09-26 18:26 ` 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=OF797DFD92.6C4D6303-ONC1256AD4.003B136C@de.ibm.com \
--to=djbarrow@de.ibm.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