[lldb-dev] What is the stop/pause command for lldb?

[Andrew MacPherson]

Just bringing this up again as I'm seeing some unexpected behavior on
startup with this on Linux and wanted to know if it's still expected or
something to investigate. I can look into it if this should be working.


andrew at host:~$ lldb /usr/bin/python
Current executable set to '/usr/bin/python' (x86_64).
(lldb) r
Process 22284 launching
Process 22284 launched: '/usr/bin/python' (x86_64)
Process 22284 stopped
Python 2.7.5+ (default, Feb 27 2014, 19:37:08)
[GCC 4.8.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> (lldb)
  ^^^^^
  I would expect to be at a Python prompt here, not lldb. Ctrl-C does
nothing.

error: No auto repeat.
(lldb) process interrupt
Process 22284 stopped
* thread #1: tid = 22284, 0x00007f869ef0adc3 libc.so.6`__select + 19, name
= 'python', stop reason = signal SIGSTOP
    frame #0: 0x00007f869ef0adc3 libc.so.6`__select + 19
libc.so.6`__select + 19:
-> 0x7f869ef0adc3:  cmpq   $-0xfff, %rax
   0x7f869ef0adc9:  jae    0x7f869ef0adff            ; __select + 79
   0x7f869ef0adcb:  retq
   0x7f869ef0adcc:  subq   $0x8, %rsp
(lldb) c
Process 22284 resuming

>>>
  ^^^^^
  Now at a Python prompt, hitting Ctrl-C works as expected.

>>> Process 22284 stopped
* thread #1: tid = 22284, 0x00007f869ef0adc3 libc.so.6`__select + 19, name
= 'python', stop reason = signal SIGSTOP
    frame #0: 0x00007f869ef0adc3 libc.so.6`__select + 19
libc.so.6`__select + 19:
-> 0x7f869ef0adc3:  cmpq   $-0xfff, %rax
   0x7f869ef0adc9:  jae    0x7f869ef0adff            ; __select + 79
   0x7f869ef0adcb:  retq
   0x7f869ef0adcc:  subq   $0x8, %rsp
(lldb)


On Mon, Feb 24, 2014 at 8:07 AM, Matthew Gardiner <mg11 at csr.com> wrote:

> jingham at apple.com wrote:
>
>> Control-C is currently broken in TOT lldb.  It pops the input reader for
>> the program you are debugging off the stack, but doesn't interrupt it,
>> leaving you in a kind of odd state...
>>
>> Greg's on this.
>>
>> Jim
>>
> Thanks for this, Jim.
>
> However, this leaves me a bit puzzled. Surely, if lldb *already* has a
> command intended to SIGTRAP the inferior (i.e. process interrupt), then why
> is Control-C broken? What is Control-C's intended purpose in lldb?
>
>
> Matt
>
>
>
> Member of the CSR plc group of companies. CSR plc registered in England
> and Wales, registered number 4187346, registered office Churchill House,
> Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
> More information can be found at www.csr.com. Keep up to date with CSR on
> our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people,
> YouTube, www.youtube.com/user/CSRplc, Facebook,
> www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at
> www.twitter.com/CSR_plc.
> New for 2014, you can now access the wide range of products powered by
> aptX at www.aptx.com.
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140314/4d015035/attachment.html>