From: Eli Zaretskii <eliz@delorie.com>
To: DJBARROW@de.ibm.com
Cc: gdb-patches@sourceware.cygnus.com, schwidefsky@de.ibm.com,
binutils@sourceware.cygnus.com, bfd-local@cygnus.com,
nickc@cygnus.com
Subject: Re: [PRELIMINARY]: Patch to add bfd support for IBM s390
Date: Fri, 25 Aug 2000 04:09:00 -0000 [thread overview]
Message-ID: <200008251108.HAA23656@indy.delorie.com> (raw)
In-Reply-To: <C1256946.003B1AC3.00@d12mta09.de.ibm.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]
> From: DJBARROW@de.ibm.com
> Date: Fri, 25 Aug 2000 12:45:32 +0200
>
> The breakpoint.c kludge I did as far as I remember is probably
> unwanted, I just found that the hardware breakpoints in 4-18 were in
> absolutely terrible shape staying in when not wanted & disappearing
> for no reason, has this code improved ?
I think that watchpoint-related code in GDB improved _a lot_ since
v4.18, but I'm not sure how relevant these improvements are for the
S/390 port. The watchpoint support is certainly much better for
x86-based targets, one of which I maintain.
If you can describe in more detail what problems did you see in v4.18,
it will be possible to tell you which problems are now resolved.
From DJBARROW@de.ibm.com Fri Aug 25 04:58:00 2000
From: DJBARROW@de.ibm.com
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sourceware.cygnus.com, nickc@cygnus.com, Michael Snyder <msnyder@redhat.com>
Subject: Re: [PRELIMINARY]: Patch to add bfd support for IBM s390
Date: Fri, 25 Aug 2000 04:58:00 -0000
Message-id: <C1256946.0041A357.00@d12mta09.de.ibm.com>
X-SW-Source: 2000-08/msg00313.html
Content-length: 706
If this code has improved my kludges are probably obselete.
To be honest it was a long time ago, it was primarily to do with
watchpoints set up in hw being
inconsistent with what info watchpoints said was active.
e.g. The watchpoint code cleaned the hardware breakpoints in the next run
while info watchpoints
still reported watchpoints active ( this kind of stuff ), unfortunately I
cant remember exactly just cast
asparagus.
I'll do some testing over the next few days & if it still looks unhealthy
I'll start complaining.
D.J. Barrow 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 prev parent reply other threads:[~2000-08-25 4:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-25 3:46 DJBARROW
2000-08-25 4:09 ` Eli Zaretskii [this message]
[not found] <C1256946.00620C31.00@d12mta09.de.ibm.com>
2000-08-25 11:02 ` Michael Snyder
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=200008251108.HAA23656@indy.delorie.com \
--to=eliz@delorie.com \
--cc=DJBARROW@de.ibm.com \
--cc=bfd-local@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=nickc@cygnus.com \
--cc=schwidefsky@de.ibm.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