• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Threads, stdin and interaction of gdb
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Threads, stdin and interaction of gdb


  • Subject: Threads, stdin and interaction of gdb
  • From: Mark Smithfield <email@hidden>
  • Date: Sun, 28 May 2006 13:46:38 -0700 (PDT)

The goal:
to drive the state of the program using cmds from
stdin into a lua interpreter.

The attempt:
* create a thread which listens to stdin using
fgets().

* thread fills a buffer and then uses a mutex and
condition to indicate that the buffer is
ready to be consumed.

* a timer in the main event loop calls a routine which
consumes this buffer

* a lua interpreter is called with the string


And everything worked fine until I tried to debug it
:)


When gdb runs the app, gdb is using stdin, and it
doesn't seem that the fgets() in the
thread gets any of the input.

Threads, stdin, unix system calls and the interaction
of gdb with an app under xcode.

Since any questions that begin, "I'm using xcode
to..." is going to be met with derision elsewhere, I
ask here. And I am asking only because I am quite
stumped.

The question:
* is there any reason why this is clearly not possible

* if it is possible, where should I look for more
information.

Much thanks in advance.
Mark


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: warning multiple definitions of symbol ___cxa_atexit and _atexit - why?
  • Next by Date: Errors & Warning Smart Group with external targets
  • Previous by thread: warning multiple definitions of symbol ___cxa_atexit and _atexit - why?
  • Next by thread: Errors & Warning Smart Group with external targets
  • Index(es):
    • Date
    • Thread