Just FYI, the reference to db_interface.cxx actually isn't bogus. It's the entry point for the kernel debugger.
What's going on is that the reader has finished and is exiting gracelessly. I need to clean up the test case.
Bengt Kleberg <firstname.lastname@example.org> on 02/15/99 11:30:32 AM
cc: (bcc: Jonathan S Shapiro/Watson/IBM) Subject: Re: eros-0.8.1, tests/perf/bw_pipe
I am sorry to report that I failed to understand what constitutes a
After having seen one (iocall) I now realise taht bw_pipe failed :-(
The end look like this:
Reader Done -- <lots> bytes
Call to destroy...
InvokeMyKeeper(): thread takes seg flt with no kpr
Current thread 0x00213000 (running) ctxt 0x00205cc0 (user) rsrv=0x001fe300 uobj 0x0000018 0x000133040000000
Stopped at 0x00105854 Debugger*void)+4 [db_interface.cxx:262]" movl
The reference to db_interface.cxx:262 looks bogus?