This is the mail archive of the 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: [RFA] Async mode fixes.

 > > My changes aren't just for Linux, but an exec target.  I mean native
 > > debugging (I think) with just one implementation - linux.  It sounds like
 > > I'm inflating what I've done but other native targets can presumably be
 > > adapted to make use of the changes in inf-ptrace.c, exec.c etc.
 > I think you mean "child" target?  target exec just reads an exec file
 > on disk.

Well, my changes are in exec.c to exec_ops methods, not to target methods in
inf-child.c.  Then ISTR these get inherited by target methods in inf-ptrace.c

Are you saying that these changes should really be in inf-child.c or just that
I've misunderstood the concept of an exec target?

 > > If all targets could run asynchronously, then it seems that that mode should
 > > be specified at startup:
 > > 
 > >    gdb --async myprog
 > Can it just be the default, once we get it working?  If I understand
 > correctly, the async-ness of the target should not affect the CLI at
 > all.  It lets you use "continue&" in addition to "continue", but
 > existing commands should keep working as before.
 > Async mode seems inherently superior.

You're probably right.  I just don't really have the bigger picture to be able
to say that.


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