Mail Archives: djgpp/1996/06/13/20:22:45
Reply to message 1219542 from ELIZ AT IS DOT ELTA DOT CO DOT IL on 06/13/96 2:16AM
Thank you, Eli, for the patch. I had some difficulty installing it - patch
gave me some errors and I had to manually put in the 'tryagain:' label,
but once I got it installed it solved the printer off problem beautifully.
BTW, if anybody would like a copy of my (now working) printer echo
library, just send me email and I'll arrange to have it uploaded somewhere.
The advantage of it over something like script is that you can choose
whether to echo any given piece of text by simply calling the standard
printf, etc., instead of my wrapper functions. I still need to write some
documentation for it, though (including the problem of working under
QDPMI.)
FYI, the port of script that is on SimTel is so old that it was written for
DOS 3.2. I would undertake the task of porting it to DJGPP except that
I am still only barely familiar with RM->PM assembly conversion. If
anyone would like to update this six-year old program, I'd be very
grateful. :)
One other point, though:
>Neither GDB docs nor the sources don't seem to tell anything about GDB
>being able to set the default source directories from the environment, at
>least not in version 4.12 (which is the one ported to DJGPP). The default
>value is always the current directory and the compilation directory
>recorded inside the debuggee (if any).
I figured out how to do this by using the 'set directory' command within the
gdb.ini file. The only problem is that for some reason, when it reads in the
set of directories, gdb seems to completely ignore them (at least when they
contain valid directories). When I use an environment variable as part
of the pathname, for example, gdb accepts it, but when I use a valid
directory it just ignores it. For example:
[...]
set directory $DJGPP/src/libc/ansi/stdio
works, but this does not:
[...]
set directory /djgpp/src/libc/ansi/stdio
However, when I type those lines while inside gdb, they are both accepted.
I have not yet been able to determine if they actually _work_, because
it doesn't look like libc.a actually includes complete debugging information.
Also, directory seems unable to recognize DOS drive specifiers. If I try
to type a line like this:
set directory c:/djgpp/src/libc/ansi/stdio
It interprets 'c' as a separate pathname which it then (for some reason)
expands into the current directory. Very disconcerting, and potentially
dangerous if one happens to be working on a different drive.
Anyway, enough for now.
John
- Raw text -