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]

should xfer_memory vector functions perform multiple transfers?


In many (most? (all?)) cases, the xfer_memory vector functions will
perform multiple transfers if the size of the transfer is too large
to do in one.  The high level logic in target_xfer_memory() will do
the same.  

Is there a rule about whether a too-large transfer should be split by
xfer_memory vector functions or target_xfer_memory()?  If it can be
done by vector functions, the value of target_xfer_memory_partial() 
is limited.  (target_xfer_memory_partial() is used (indirectly) in
generic_load() so that GDB is not completely stalled during large
transfers.

        --jtc

-- 
J.T. Conklin
RedBack Networks

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