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] |
>Could you explain why you this is necessary?
>I'm guessing in the File I/O case this handles the user hitting C-c >while the client is processing a request, and there is considerable >complexity involved in reporting whether the I/O has completed. But >using errno doesn't make any sense in the symbol lookup context and it >seems to me easier to make GDB delay sending the C-c to the target >until the qSymbol has been processed: > -> c > <- qSymbol:AAAAAAAAAAAAA > Control-C > -> qSymbol:AAAAAAAAAAAAA:012131312 > -> \003
Here's the problem:
I did read the manual when you referenced it, you don't need to paste the whole thing :)
A user trying to cntrl-c GDB while GDB is taking its time looking up a symbol isn't theory. There needs to be an error/abort mechanism and adopting "F" provides that.
The alternative is to specify some sort of customized q packet semantics - giving two callbacks and two different behaviors - I'm really not interested in going there.
Perhaps you've noticed that we have hashed minimal symbol table lookups? There is no excuse for symbol table lookups to take long enough for there to need to be an abort mechanism. This is in contrast to file I/O which can block.
I don't think we need to use the heavy-weight mechanism which supports interruption for operations that don't need to be interrupted, and I can't see a reason to support interruption of this lookup. If you do, please enlighten me.
You need to handle such race conditions anyway.
-> c <- qSymbol | cntrl-c ->
That's a different problem, and it is already correctly handled by gdbserver. We'll write out the qSymbol, read in the Ctrl-C, signal the inferior, look again for an ACK, eventually get the ACK. Then we'd wait for and get a qSymbol reply, resume the suspended thread that made the lookup request, wait for it, and see the SIGINT we created.
- <retry><cntrl-C> - <symbol><cntrl-C>
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |