This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] Non-executable stack on SPARC
- From: "Eli Zaretskii" <eliz at elta dot co dot il>
- To: Mark Kettenis <kettenis at chello dot nl>
- Cc: gdb at sources dot redhat dot com
- Date: Sun, 01 Feb 2004 22:08:49 +0200
- Subject: Re: [RFC] Non-executable stack on SPARC
- References: <200401252350.i0PNoB1O021806@elgar.kettenis.dyndns.org> <uad4b2odj.fsf@elta.co.il> <200401261242.i0QCgUoB026534@elgar.kettenis.dyndns.org> <uad49omd7.fsf@elta.co.il> <200402011748.i11HmJRR000558@elgar.kettenis.dyndns.org>
- Reply-to: Eli Zaretskii <eliz at elta dot co dot il>
> 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.