Messages in this thread |  | | | Date | Sat, 25 Jul 1998 01:37:52 +0200 | | From | (Carsten Gross) | | Subject | /proc/parport/x/autoprobe lets you peek into userspace mem. |
| |
Hi!
I am just compiling some KDE archives (load av. 2, a lot of memory usage) and looking around a little bit:
(My Kernel is 2.1.110-SMP, parport + IEEE1284 readback, printer is attached, but off since boot):
python:/proc/parport/0>cat autoprobe # just try often, after 10-20 times void moveBottomLeft( const QPoint &p ); void moveCenter( const QPoint &p ); void moveBy( int dx, int dy );
void setRect( int x, int y, int w, int h ); void setCoords( int x1, int y1, int x2, int y2 ); [..more KDE code ...]
Sometimes it is some other C++-code from KDE, assembler, preprocessor stuff or just some binary characters. I think this is a peek into unused or user memory and this should not happen ;-). Please have a look at it.
If you use 'strace', this problem should be a lot more obvious. If there is no printer attachted the first read should return 0(?) because the autoprobe file is empty? Yes, this is a question, but IMHO it makes sense, that the autoprobe file is empty, if there is no printer attachted.
Thanks
Carsten
-- Linux, WinNT and MS-DOS. The Good, The Bad and The Ugly Carsten Gross carsten@sol.wohnheim.uni-ulm.de Wohnheim Heilmeyersteige Sebastian Kneipp Weg 6, 89075 Ulm
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
|  |