This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Non-executable stack on SPARC

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.

Yes.

Here, though, we don't have the case of a just-executed breakpoint, rather we have a not-yet-executed segmentation fault. To implement VM based breakpoints and watchpoints GDB will need to be able to differentiate between the two. Hence, I think making this edge case visible in infrun is better.

enjoy,
Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]