Hi Tomasz, I've also noticed there is only one tgtd process when running it in the foreground.
Running in the foreground has been the only way I've been successful in collecting core files in the past. I still do not (read: never actually spent time looking) understand the why/what differences is between foreground and why there is two processes while in background. I would have to assume that there is some sort of race condition or handshake issue between the two processes within your test senerio. Sorry I can't be of much help. Cheers Mark On Mon, Jun 30, 2008 at 7:00 PM, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote: > Mark Harvey schrieb: >> My 2c worth. >> >> Try running the tgtd in 'foreground' mode (after setting "ulimit -c >> unlimited"). >> >> You will then get a core file which should be a little easier to work >> with (vs gdb on a running tgtd instance). >> e.g. > > It doesn't crash when started in the foreground mode. > > Also, when started in the foreground mode, we only have one tgtd > process, so perhaps this somehow makes the issue harder or impossible to > reproduce. > > > -- > Tomasz Chmielewski > http://wpkg.org > _______________________________________________ > Stgt-devel mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/stgt-devel > _______________________________________________ Stgt-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/stgt-devel
