I guess that I see something that is 'normal', because I observerd the same
thing without my program running. As you can see, I setted a breackpoint on
ds_device_write and letted the kernel continue. After some time the
breakpoint was hit with the result: kmsg != kmsg->ikm_next->ikm_prev.
wagi
I checked out latest cvs today and noticed something I found odd in
hurd/hurd/fsys_reply.defs:
simpleroutine fsys_startup_reply (
repsy_port: reply_port_t; // <-- misspelling of reply_port??
retcode: kern_return_t;
realnode: mach_port_send_t);
simpleroutine fsys_s
Title: ¡ØDVDjoa.com12¿ù Ãâ½Ã¿¹Á¤ÀÛ¡Ø
DVDjoa.com Title News
[2001³â12¿ùÈ£]
[ÁøÁÖ¸¸]Ãâ½Ã¿¹Á¤ÀÏ:
12¿ù10ÀÏ
ÁÖ¿¬: º¥ ¿¡Ç÷º/Á¶½¬ ÇÏÆ®³Ý/ÄÉÀÌÆ® º£Å²¼¿
¼ÒÀå°¡Ä¡: ¡Ú¡Ú¡Ú¡Ú¡Ú
ÈýÆ®¿¹°¨: ÇÑÁ¤¼ö·®! ¸¶°¨ÀÌ ÀÓ¹Ú!
ÆǸŰ¡°Ý: 24,000¿ø
Áö±Ý ÁÖ¹®Çϼ¼¿ä!
[¿±±âÀûÀÎ
±×³à]Ãâ½Ã¿¹Á¤ÀÏ: 12
