hello,everyone,I'm reading LDD3.Topics about oops,it said the code bellow would cause a fault condition because "this method copies a string to a local variable,unfortunately,the string is longer than the destination array".Well,hard to understand....Is that right?I thought the fault should be caused by the wrong memset,it overwrite the function stack,the value of __user is 0xff now.will anyone tell me what happened here?Thanks;
Solaris 2.6, using CDE:
agh. I accidentally set an ugly palette as my Home Session. The problem is, when I change the palette back to Default, I am informed that my change will be apparent in my next session. But when I log out and in, it's still the Ugly Palette. Doesn't matter if I set the... (1 Reply)
When ever i mount any of my 2 scsi cdroms, I get a kernel crash with the folfollowing oops kernel output.
I understand that it is impossible to anwser my question WHY but could you give me some advice where i should look to debug the problem or advice me some tools to detect what might be... (3 Replies)
I have directory/dns server running sparc solaris 9.
while troubleshooting another issue, i overwrote the aliases file on accident.
my question is: is there any way to revert this?
any help super appreciated...especially since this a production box! (2 Replies)
Hi All,
Can any one please differenciate between the Data Abstraction and Encapsulation? If possible, with code.
Thanks in Advance,
Naga:cool: (2 Replies)
I've been tearing my hair out over this: vsftp does not work on any of my RedHat Server 5.x systems - I keep getting a variation on 500 OOPS: vsftpd: cannot locate user specified in 'ftp_username':ftp or 500 OOPS: cannot locate user entry:nobody (different errors on different systems). I spent... (2 Replies)
Hi all,
When i load my block device driver in Fedoracore10 kernel 2.6.27. i got this type of error kernel panic - not syncing : Fatal exception in interrupt. I am unable to save the log file....
Can any one help me.....
regards
sundar (4 Replies)
I can belive I really did this... chmod 777 /home :eek:
I have my /home directory synced to another machine.
Can anyone tell me how to get the permissions from
back up server /home to production server /home
It's important that I dont over write the files on the... (1 Reply)
I've been fighting this for about a year: vsftp does not work on any of my RedHat Server 5.x systems - I keep getting a variation on 500 OOPS: vsftpd: cannot locate user specified in 'ftp_username':ftp or 500 OOPS: cannot locate user entry:nobody (different errors on different systems). I spent... (0 Replies)
Discussion started by: thomn8r
0 Replies
LEARN ABOUT BSD
mkstr
MKSTR(1) General Commands Manual MKSTR(1)NAME
mkstr - create an error message file by massaging C source
SYNOPSIS
mkstr [ - ] messagefile prefix file ...
DESCRIPTION
Mkstr is used to create files of error messages. Its use can make programs with large numbers of error diagnostics much smaller, and
reduce system overhead in running the program as the error messages do not have to be constantly swapped in and out.
Mkstr will process each of the specified files, placing a massaged version of the input file in a file whose name consists of the specified
prefix and the original name. A typical usage of mkstr would be
mkstr pistrings xx *.c
This command would cause all the error messages from the C source files in the current directory to be placed in the file pistrings and
processed copies of the source for these files to be placed in files whose names are prefixed with xx.
To process the error messages in the source to the message file mkstr keys on the string `error("' in the input stream. Each time it
occurs, the C string starting at the `"' is placed in the message file followed by a null character and a new-line character; the null
character terminates the message so it can be easily used when retrieved, the new-line character makes it possible to sensibly cat the
error message file to see its contents. The massaged copy of the input file then contains a lseek pointer into the file which can be used
to retrieve the message, i.e.:
char efilname[] = "/usr/share/pascal/pi_strings";
int efil = -1;
error(a1, a2, a3, a4)
{
char buf[256];
if (efil < 0) {
efil = open(efilname, 0);
if (efil < 0) {
oops:
perror(efilname);
exit(1);
}
}
if (lseek(efil, (long) a1, 0) || read(efil, buf, 256) <= 0)
goto oops;
printf(buf, a2, a3, a4);
}
The optional - causes the error messages to be placed at the end of the specified message file for recompiling part of a large mkstred pro-
gram.
SEE ALSO lseek(2), xstr(1)3rd Berkeley Distribution October 22, 1996 MKSTR(1)