<div class="gmail_quote">On Sat, Sep 18, 2010 at 5:58 AM, Tom Lichti <span dir="ltr"><<a href="mailto:redpepperracing@gmail.com">redpepperracing@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">(gdb) thread 2</div>
[Switching to thread 2 (Thread 0x2ec9b70 (LWP 3157))]#1 0x02068536 in<br>
__poll (fds=0xb4b01d88, nfds=1, timeout=-1) at<br>
../sysdeps/unix/sysv/linux/poll.c:87<br>
87 int result = INLINE_SYSCALL (poll, 3, CHECK_N (fds, nfds),<br>
nfds, timeout);<br>
(gdb) print *fds<br>
$6 = {fd = 0, events = 1, revents = 0}<br>
(gdb) print fds<br>
$7 = (struct pollfd *) 0xb4b01d88<br>
(gdb) print nfds<br>
$8 = 1<br></blockquote><div><br></div><div>Hmmm, seems to be blocked waiting for input on stdin. No clue why it would be trying to do that.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
What is the process id? Or am I missing something?<br></blockquote><div><br></div><div>The same pid you attached to in gdb. Do "lsof -p pid" with that number after the -p.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<USN>uuid:1216ac5d-850f-411e-81d3-34172d45c05e::urn:schemas-upnp-org:device:MediaServer:1</USN><br></blockquote><div><br></div><div>OK, that's what I thought. :) The good news is: I have a commit going in this morning that should keep this from happening. The issue seems to be when it tries to destroy an HTTP Server thread that we don't even need, and failed startup (probably due to another similar process having the port open). This is during the SSDP search (UPnP backend searching), and it's only even tried with the USN set in the config.xml.</div>
<div><br></div><div>My change removes the HTTP server completely, so it will no longer be conflicting with each other, nor failing to be destroyed. So after I have breakfast, then get a chance to commit the changes, this hopefully will be gone.</div>
</div>