From: "Eli Zaretskii" <eliz@elta.co.il>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] Non-executable stack on SPARC
Date: Sun, 01 Feb 2004 20:13:00 -0000 [thread overview]
Message-ID: <9003-Sun01Feb2004220849+0200-eliz@elta.co.il> (raw)
In-Reply-To: <200402011748.i11HmJRR000558@elgar.kettenis.dyndns.org> (message from Mark Kettenis on Sun, 1 Feb 2004 18:48:19 +0100 (CET))
> Date: Sun, 1 Feb 2004 18:48:19 +0100 (CET)
> From: Mark Kettenis <kettenis@chello.nl>
>
> My line of thought is that it's IMHO fundamentally wrong to push
> target- or architecture-specific details into the application level of
> GDB, which is what infrun.c is. infrun.c should deal with high-level
> logic of handling a stopped inferior, it should not IMHO know about
> intricacies of specific targets.
>
> The question is to what extent this is an intricacy of a specific
> target.
I think that the set of signals, apart of SIGTRAP, that can express a
breakpoint on a given target/architecture is something infrun.c
shouldn't know about.
next prev parent reply other threads:[~2004-02-01 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 23:50 Mark Kettenis
2004-01-25 23:59 ` Daniel Jacobowitz
2004-01-26 6:51 ` Eli Zaretskii
2004-01-26 6:51 ` Eli Zaretskii
2004-01-26 12:42 ` Mark Kettenis
2004-01-27 8:16 ` Eli Zaretskii
2004-02-01 17:48 ` Mark Kettenis
2004-02-01 20:13 ` Eli Zaretskii [this message]
2004-02-02 18:37 ` Andrew Cagney
2004-01-26 16:21 ` Andrew Cagney
2004-01-27 8:00 ` Eli Zaretskii
2004-02-01 17:54 ` Mark Kettenis
2004-02-02 18:27 ` 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=9003-Sun01Feb2004220849+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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