473,320 Members | 2,177 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,320 software developers and data experts.

segementation fault

My Program seemed to be working without much problem until I used the
wide character functions wchar_t wcscpy(wchar_t *to, wchar_t *from) and
int wctob(win_t *c).

May 10 '06 #1
23 1859
Just a thought: wide characters are, well, wide - did you allocate
enough space to handle the wideness?

May 10 '06 #2
didier2309 wrote:

My Program seemed to be working without much problem until I used the
wide character functions wchar_t wcscpy(wchar_t *to, wchar_t *from) and
int wctob(win_t *c).


Define "seemed to be working".

Why does it no longer "seem to be working"?

You have an error on line 42.

--
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody | www.hvcomputer.com | |
| kenbrody/at\spamcop.net | www.fptech.com | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+
Don't e-mail me at: <mailto:Th*************@gmail.com>

May 10 '06 #3
didier2309 wrote:
My Program seemed to be working without much problem until I used the
wide character functions wchar_t wcscpy(wchar_t *to, wchar_t *from) and
int wctob(win_t *c).


You have an error on line 42. In other words, how are we supposed to see
what you have done wrong if we can't see your code?
--
Flash Gordon, living in interesting times.
Web site - http://home.flash-gordon.me.uk/
comp.lang.c posting guidelines and intro:
http://clc-wiki.net/wiki/Intro_to_clc
May 10 '06 #4
It executes till the statement wcpcpy(laccnum, L"000-00-0001");

int acopen::open_acc()
{
int accnum;
char stname[80];
FILE *getaccnum;
getaccnum = fopen("numbers", "r");
if(getaccnum == NULL){
cout << "No account has been openned yet\n";
wcpcpy(lacc_num, L"000-00-0001");
}
else{
fseek(getaccnum, 11, SEEK_END);
fscanf(getaccnum, "%S", lacc_num);
int sec[9], accnum;
sec[0] = wctob(lacc_num[0]);
sec[1] = wctob(lacc_num[1]);
sec[2] = wctob(lacc_num[2]);
sec[3] = wctob(lacc_num[4]);
sec[4] = wctob(lacc_num[5]);
sec[5] = wctob(lacc_num[7]);
sec[6] = wctob(lacc_num[8]);
sec[7] = wctob(lacc_num[9]);
sec[8] = wctob(lacc_num[10]);
for(int i = 0; i < 9; i--){
accnum = accnum*10 +sec[i] ;
}

int tempaccnum;

accnum = accnum++;
tempaccnum = accnum;
for(int i = 8; i >= 0; i--){
sec[i] = tempaccnum - (tempaccnum/10)*10;
tempaccnum = tempaccnum/10;
}
lacc_num[0] = btowc(sec[0]);
lacc_num[1] = btowc(sec[1]);
lacc_num[2] = btowc(sec[2]);
lacc_num[3] = '-';
lacc_num[4] = btowc(sec[3]);
lacc_num[5] = btowc(sec[4]);
lacc_num[6] = '-';
lacc_num[7] = btowc(sec[5]);
lacc_num[8] = btowc(sec[6]);
lacc_num[9] = btowc(sec[7]);
lacc_num[10] = btowc(sec[8]);
lacc_num[11] = '\0';

}
fclose(getaccnum);
FILE *putn;
putn = fopen("numbers","ab");
if(putn == NULL){
cout << "\ncannnot open file\n";
return 1;
}
FILE *out;
out = fopen("account","ab");
if(out == NULL) {
cout << "\ncannot open file";
return 1;
}
cout <<"\nthe account number is: ";
printf("%S\n",lacc_num);
cout << "enter name: \n";
cin >> sname;

cout << "enter last name\n";
cin >> slastname;

cout << "birthday? Day, month and year seperately (in
numbers)...\n";
do{
cin >> sbirth_day ;
if(!getint(sbirth_day))
badent();//call badebt()
}while(!getint(sbirth_day));

do{
cin >> sbirth_month ;
if(!getint(sbirth_month))
badent();
}while(!getint(sbirth_month));

do{
cin >> sbirth_year;
if(!getint(sbirth_year))
badent();
}while(!getint(sbirth_year));

cout << "street address?(house number and street name only:
Enter [space]~ to end address) \n";
cin >> shousenum ;
do{
cin >> stname;
strcat(sstreetname, stname);
strcat(sstreetname, " ");
}while(strcmp(stname,"~"));
cout << "city?\n";
cin >>scity;

do{
cout <<"zipcode?\n";
cin >> szip;
}while(!getlong(szip));

cout << "phone and area code?\n";
do{
cin >> sphone;
if(!getlong(sphone))
badent();
}while(!getlong(sphone));

do{
cin >> sarea ;
if(!getint(sarea))
badent();
}while(!getint(sarea));

do{
cout << "social security?\n";
cin >>ssocial;
}while(!getlong(ssocial));

do{
cout << "deposit amount?\n";
cin >>sbalance;
}while(!(getfloat(sbalance)));
fprintf(out, "%S\n", lacc_num);
fprintf(putn, "%S\n", lacc_num);
fprintf(out ,"%s\n", sname);
fprintf(out ,"%s\n", slastname);
fprintf(out, "%s\n", sbirth_day);
fprintf(out, "%s\n", sbirth_month);
fprintf(out, "%s\n", sbirth_year);
fprintf(out, "%s\n", sstreetname);
fprintf(out, "%s\n", shousenum);
fprintf(out, "%s\n", scity);
fprintf(out, "%s\n", szip);
fprintf(out, "%s\n", sphone);
fprintf(out, "%s\n", sarea);
fprintf(out, "%s\n", ssocial);
fprintf(out, "%s\n", sbalance);
fclose(putn);
fclose(out);
return 0;
}

May 10 '06 #5
didier2309 wrote:
It executes till the statement wcpcpy(laccnum, L"000-00-0001");

int acopen::open_acc()


[snip C++ code]

Sorry, this isn't comp.lang.c.and.all.its.derivatives, try
comp.lang.c++.

Robert Gamble

May 10 '06 #6
didier2309 wrote:
It executes till the statement wcpcpy(laccnum, L"000-00-0001");


Setting aside that you posted C++ code, your actual problem may still
be a C problem. Unfortunately there's no way to tell without knowing
how laccnum is defined, and you omitted that salient detail. It's
probably a character buffer, and knowing how big it is might be
helpful. If it's a pointer, perhaps you'd like to check for NULL?

If you're going to post C++ again, as noted there is a group for that
language.

<ot>Considering that you're using C++, you seem to like fprintf() and
its friends - why not go all the way and use the stream capability C++
so kindly provides?</ot>

May 10 '06 #7
didier2309 wrote:
My Program seemed to be working without much problem until I used the
wide character functions wchar_t wcscpy(wchar_t *to, wchar_t *from) and
int wctob(win_t *c).

It might 'seem' to be working because the OS by chance gave you memory
that had 'unallocated' memory beyond the memory range allocated to you
so it was working 'incorrectly' though. It also depends on your OS.
Easiest thing would be to try it with valgrind if you're on Linux.

Regards,
Ahmed
May 10 '06 #8
didier2309 wrote:
It executes till the statement wcpcpy(laccnum, L"000-00-0001");

int acopen::open_acc()

[etc]
Please direct questions about languages which are not C to newsgroups
other than <news:comp.lang.c>. It appears that your language is the
abominable C++, which has its own newsgroup, <news:comp.lang.c++>.
May 10 '06 #9
"didier2309" <di********@yahoo.fr> writes:
It executes till the statement wcpcpy(laccnum, L"000-00-0001");

int acopen::open_acc()
{
int accnum;
char stname[80];
FILE *getaccnum;
getaccnum = fopen("numbers", "r");
if(getaccnum == NULL){
cout << "No account has been openned yet\n";
wcpcpy(lacc_num, L"000-00-0001");
} [...] }


You need to provide context when you post a followup. See
<http://cfaj.freeshell.org/google/> to understand how and why.

The code you posted is C++, not C. You could probably convert it to
pure C; if not, you need to ask in comp.lang.c++.

You posted a single function, not a complete program. Even if it were
in C, or if I used a C++ compiler, I couldn't try it myself without
adding a main() function that calls your function, adding whatever
#include directives are required, and adding declarations for anything
you didn't declare. The resulting program would not be the same as
the one you're having problems with.

There is no declaration for lacc_num. Without knowing how it's
declared, we can't possibly guess what the problem is.

There is no wcpcpy() function in standard C <OT>or in standard
C++</OT>. I'm guessing this is a function somewhere in your own
program, or in a library you're using. Without knowing anything about
it, we can't possibly guess what the problem is.

Narrow the problem down to a small complete compilable program that
exhibits the problem. By "complete", I mean something that I can
copy-and-paste and compile and run on my own system without depending
on any non-standard libraries. If your wcpcpy() function is part of
the problem, include a definition of it in your program. If the
resulting program is C++ rather than C, post it to comp.lang.c++.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
May 10 '06 #10
didier2309 wrote:
It executes till the statement wcpcpy(laccnum, L"000-00-0001");

int acopen::open_acc()
{
int accnum;
char stname[80];
FILE *getaccnum;
getaccnum = fopen("numbers", "r");
if(getaccnum == NULL){
cout << "No account has been openned yet\n";


<snip>

You are in the wrong place. You want comp.lang.c++ down the hall third
door on the right.
--
Flash Gordon, living in interesting times.
Web site - http://home.flash-gordon.me.uk/
comp.lang.c posting guidelines and intro:
http://clc-wiki.net/wiki/Intro_to_clc

Inviato da X-Privat.Org - Registrazione gratuita http://www.x-privat.org/join.php
May 10 '06 #11
cb******@gmail.com wrote:
didier2309 wrote:
It executes till the statement wcpcpy(laccnum, L"000-00-0001");


Setting aside that you posted C++ code, your actual problem may still
be a C problem.


Please explain how a problem with C++ code could be "a C problem".

Robert Gamble

May 10 '06 #12
"Robert Gamble" <rg*******@gmail.com> writes:
cb******@gmail.com wrote:
didier2309 wrote:
> It executes till the statement wcpcpy(laccnum, L"000-00-0001");


Setting aside that you posted C++ code, your actual problem may still
be a C problem.


Please explain how a problem with C++ code could be "a C problem".


The posted code could *probably* be converted from C++ to standard C
without much difficulty (dropping the "::" from the function name,
using printf rather than "cout << ...", maybe a couple of other
things). If the resulting pure C code still exhibited the same
problem, it's reasonable to say that the problem is a "C problem" --
or, more precisely, a problem that falls within the common subset of C
and C++.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
May 10 '06 #13
On Tue, 09 May 2006 21:42:55 GMT, Keith Thompson <ks***@mib.org> wrote
in comp.lang.c:
"Robert Gamble" <rg*******@gmail.com> writes:
cb******@gmail.com wrote:
didier2309 wrote:
> It executes till the statement wcpcpy(laccnum, L"000-00-0001");

Setting aside that you posted C++ code, your actual problem may still
be a C problem.


Please explain how a problem with C++ code could be "a C problem".


The posted code could *probably* be converted from C++ to standard C
without much difficulty (dropping the "::" from the function name,
using printf rather than "cout << ...", maybe a couple of other
things). If the resulting pure C code still exhibited the same
problem, it's reasonable to say that the problem is a "C problem" --
or, more precisely, a problem that falls within the common subset of C
and C++.


Actually, the "common subset of C and C++" is off-topic here, because
C does not define or recognize it. Compatibility between C and C++ is
99.999% a C++ issue. The C standard does not define the meaning of
any similar or identical syntax, macro, or function in C. The C++
standard, and only the C++ standard, specifies which parts of C it
adopts and with what changes.

While the C standard committee accepted a mandate not to introduce
unnecessary incompatibilities between C and C++, C99 mentions "C++" in
exactly four places, all non-normative footnotes that apply to C++
implementations, not C implementations, all added at the request of
the C++ committee:

Footnote 182.

Footnote 217.

Footnote 218.

Footnote 220.

In addition, without explanation, C99 forbids a C implementation from
defining a macro with the identifier "__cplusplus" in the translator
itself, or in any standard header.

The C standard states nothing at all about the behavior of any C++
program. Nor does it define a "common subset".

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://c-faq.com/
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html
May 10 '06 #14
Jack Klein <ja*******@spamcop.net> writes:
On Tue, 09 May 2006 21:42:55 GMT, Keith Thompson <ks***@mib.org> wrote
in comp.lang.c:
"Robert Gamble" <rg*******@gmail.com> writes:
> cb******@gmail.com wrote:
>> didier2309 wrote:
>> > It executes till the statement wcpcpy(laccnum, L"000-00-0001");
>>
>> Setting aside that you posted C++ code, your actual problem may still
>> be a C problem.
>
> Please explain how a problem with C++ code could be "a C problem".


The posted code could *probably* be converted from C++ to standard C
without much difficulty (dropping the "::" from the function name,
using printf rather than "cout << ...", maybe a couple of other
things). If the resulting pure C code still exhibited the same
problem, it's reasonable to say that the problem is a "C problem" --
or, more precisely, a problem that falls within the common subset of C
and C++.


Actually, the "common subset of C and C++" is off-topic here, because
C does not define or recognize it. Compatibility between C and C++ is
99.999% a C++ issue. The C standard does not define the meaning of
any similar or identical syntax, macro, or function in C. The C++
standard, and only the C++ standard, specifies which parts of C it
adopts and with what changes.

[...etc...]

Ok, let's pretend C++ doesn't even exist.

The posted code looks very much like valid C, with a few exceptions,
including a function name containing "::" and some odd-looking
left-shift operations. The non-C things in the code are probably not
germane to the actual problem. If the code were corrected so as to be
conforming C, it's quite possible that the original problem, whatever
it might be, would be unaffected. If so, I'd call that "a C problem".

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
May 10 '06 #15
Keith Thompson wrote:
Jack Klein <ja*******@spamcop.net> writes:
On Tue, 09 May 2006 21:42:55 GMT, Keith Thompson <ks***@mib.org> wrote
in comp.lang.c:
"Robert Gamble" <rg*******@gmail.com> writes:
cb******@gmail.com wrote:
> didier2309 wrote:
>> It executes till the statement wcpcpy(laccnum, L"000-00-0001");
> Setting aside that you posted C++ code, your actual problem may still
> be a C problem.
Please explain how a problem with C++ code could be "a C problem".
The posted code could *probably* be converted from C++ to standard C
without much difficulty (dropping the "::" from the function name,
using printf rather than "cout << ...", maybe a couple of other
things). If the resulting pure C code still exhibited the same
problem, it's reasonable to say that the problem is a "C problem" --
or, more precisely, a problem that falls within the common subset of C
and C++.

Actually, the "common subset of C and C++" is off-topic here, because
C does not define or recognize it. Compatibility between C and C++ is
99.999% a C++ issue. The C standard does not define the meaning of
any similar or identical syntax, macro, or function in C. The C++
standard, and only the C++ standard, specifies which parts of C it
adopts and with what changes.

[...etc...]

Ok, let's pretend C++ doesn't even exist.

The posted code looks very much like valid C, with a few exceptions,
including a function name containing "::" and some odd-looking
left-shift operations. The non-C things in the code are probably not
germane to the actual problem. If the code were corrected so as to be
conforming C, it's quite possible that the original problem, whatever
it might be, would be unaffected. If so, I'd call that "a C problem".

FWIW, I got your meaning. The problem the OP is running into is likely
not syntax, but the improper use of a standard C call.
May 10 '06 #16
"void * clvrmnky()" <cl**************@hotmail.com.invalid> writes:
Keith Thompson wrote:
Jack Klein <ja*******@spamcop.net> writes:
On Tue, 09 May 2006 21:42:55 GMT, Keith Thompson <ks***@mib.org> wrote
in comp.lang.c:

"Robert Gamble" <rg*******@gmail.com> writes:
> cb******@gmail.com wrote:
>> didier2309 wrote:
>>> It executes till the statement wcpcpy(laccnum, L"000-00-0001");
>> Setting aside that you posted C++ code, your actual problem may still
>> be a C problem.
> Please explain how a problem with C++ code could be "a C problem".
The posted code could *probably* be converted from C++ to standard C
without much difficulty (dropping the "::" from the function name,
using printf rather than "cout << ...", maybe a couple of other
things). If the resulting pure C code still exhibited the same
problem, it's reasonable to say that the problem is a "C problem" --
or, more precisely, a problem that falls within the common subset of C
and C++.
Actually, the "common subset of C and C++" is off-topic here, because
C does not define or recognize it. Compatibility between C and C++ is
99.999% a C++ issue. The C standard does not define the meaning of
any similar or identical syntax, macro, or function in C. The C++
standard, and only the C++ standard, specifies which parts of C it
adopts and with what changes.

[...etc...]
Ok, let's pretend C++ doesn't even exist.
The posted code looks very much like valid C, with a few exceptions,
including a function name containing "::" and some odd-looking
left-shift operations. The non-C things in the code are probably not
germane to the actual problem. If the code were corrected so as to be
conforming C, it's quite possible that the original problem, whatever
it might be, would be unaffected. If so, I'd call that "a C problem".

FWIW, I got your meaning. The problem the OP is running into is
likely not syntax, but the improper use of a standard C call.


What standard C call? (wcpcpy is not standard, and the OP didn't show
us its definition.)

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
May 10 '06 #17
On 2006-05-10, Keith Thompson <ks***@mib.org> wrote:
"void * clvrmnky()" <cl**************@hotmail.com.invalid> writes:
Keith Thompson wrote:
Jack Klein <ja*******@spamcop.net> writes:
On Tue, 09 May 2006 21:42:55 GMT, Keith Thompson <ks***@mib.org> wrote
in comp.lang.c:

> "Robert Gamble" <rg*******@gmail.com> writes:
>> cb******@gmail.com wrote:
>>> didier2309 wrote:
>>>> It executes till the statement wcpcpy(laccnum, L"000-00-0001");
>>> Setting aside that you posted C++ code, your actual problem may still
>>> be a C problem.
>> Please explain how a problem with C++ code could be "a C problem".
> The posted code could *probably* be converted from C++ to standard C
> without much difficulty (dropping the "::" from the function name,
> using printf rather than "cout << ...", maybe a couple of other
> things). If the resulting pure C code still exhibited the same
> problem, it's reasonable to say that the problem is a "C problem" --
> or, more precisely, a problem that falls within the common subset of C
> and C++.
Actually, the "common subset of C and C++" is off-topic here, because
C does not define or recognize it. Compatibility between C and C++ is
99.999% a C++ issue. The C standard does not define the meaning of
any similar or identical syntax, macro, or function in C. The C++
standard, and only the C++ standard, specifies which parts of C it
adopts and with what changes.
[...etc...]
Ok, let's pretend C++ doesn't even exist.
The posted code looks very much like valid C, with a few exceptions,
including a function name containing "::" and some odd-looking
left-shift operations. The non-C things in the code are probably not
germane to the actual problem. If the code were corrected so as to be
conforming C, it's quite possible that the original problem, whatever
it might be, would be unaffected. If so, I'd call that "a C problem".

FWIW, I got your meaning. The problem the OP is running into is
likely not syntax, but the improper use of a standard C call.


What standard C call? (wcpcpy is not standard, and the OP didn't show
us its definition.)


I'll hazard a guess:

wchar_t *
wcpcpy(wchar_t * to, const wchar_t * from)
{
»···for (; (*to = *from); ++from, ++to);
»···return(to);
}
May 10 '06 #18
Jordan Abel <ra*******@gmail.com> writes:
On 2006-05-10, Keith Thompson <ks***@mib.org> wrote:
"void * clvrmnky()" <cl**************@hotmail.com.invalid> writes: [...]
FWIW, I got your meaning. The problem the OP is running into is
likely not syntax, but the improper use of a standard C call.


What standard C call? (wcpcpy is not standard, and the OP didn't show
us its definition.)


I'll hazard a guess:

wchar_t *
wcpcpy(wchar_t * to, const wchar_t * from)
{
for (; (*to = *from); ++from, ++to);
return(to);
}


You've had some funny characters there; I replaced them with blanks.

As it happens, there's a wcpcpy() function that's part of the Linux
Standard Base Specification. (I hadn't bothered to google it until
now.) If the OP is having a problem with wcpcpy(), he needs to ask in
a Linux newsgroup. If he can re-write his code as a standard C
program, he can ask about it here. Until then, there's no point in
speculating.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
May 10 '06 #19
I don't know what valgrind is, is it included with opensuse?

May 10 '06 #20
I'm using the opensuse operating system and this function is part of
the libc standard library. and lacc_num is of type wchar_t

May 10 '06 #21
didier2309 wrote:
I don't know what valgrind is, is it included with opensuse?

Please quote context in your replies, see
<http://cfaj.freeshell.org/google/>

Try a group dedicated to your platform, your will get more help there.
This isn't a C question

--
Ian Collins.
May 10 '06 #22
On 2006-05-10, Keith Thompson <ks***@mib.org> wrote:
Jordan Abel <ra*******@gmail.com> writes:
On 2006-05-10, Keith Thompson <ks***@mib.org> wrote:
"void * clvrmnky()" <cl**************@hotmail.com.invalid> writes: [...] FWIW, I got your meaning. The problem the OP is running into is
likely not syntax, but the improper use of a standard C call.

What standard C call? (wcpcpy is not standard, and the OP didn't show
us its definition.)
I'll hazard a guess:

wchar_t *
wcpcpy(wchar_t * to, const wchar_t * from)
{
for (; (*to = *from); ++from, ++to);
return(to);
}


You've had some funny characters there; I replaced them with blanks.


Pasted from vim, i had things on to show where tabs were, and i didn't
notice because i also edited the post in vim

As it happens, there's a wcpcpy() function that's part of the Linux
Standard Base Specification. (I hadn't bothered to google it until
now.) If the OP is having a problem with wcpcpy(), he needs to ask in
a Linux newsgroup. If he can re-write his code as a standard C
program, he can ask about it here. Until then, there's no point in
speculating.

May 11 '06 #23
"didier2309" <di********@yahoo.fr> writes:
I'm using the opensuse operating system and this function is part of
the libc standard library. and lacc_num is of type wchar_t


What function?

It's very difficult to understand what you're talking about if you don't
provide context. Read <http://cfaj.freeshell.org/google/>.

I think you're talking about the "wcpcpy" function. That function is
not defined by the C standard, so we can't help you with it here.
(The "libc standard library" contains a number of functions that
aren't specified by the C language standard.)

Here's what you need to do (I've told you this already):

Write a small, complete, compilable self-contained program that
illustrates whatever problem you're having. I suggest writing it in
pure C, not C++, unless you actually need to use some C++ features. A
complete program *must* include a main() function, and I must be able
to copy-and-paste it from your article and compile and run it on my
own system.

What you've done so far is post an incomplete code fragment. Telling
us that lacc_num is of type wchar_t is not enough; we don't know where
it's declared, how it's initialized, or anything else.

If the program depends on a system-specific function like "wcpcpy",
post it to a system-specific newsgroup; in your case, probably one
with "linux" in its name.

A few useful links:

http://www.ungerhu.com/jxh/clc.welcome.txt
http://benpfaff.org/writings/clc/off-topic.html
http://cfaj.freeshell.org/google/
http://clc-wiki.net/wiki/Introduction_to_comp.lang.c
http://www.catb.org/~esr/faqs/smart-questions.html

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
May 11 '06 #24

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

5
by: Fra-it | last post by:
Hi everybody, I'm trying to make the following code running properly, but I can't get rid of the "SEGMENTATION FAULT" error message when executing. Reading some messages posted earlier, I...
0
by: Matt S | last post by:
Hello, I'm trying to build a C# client to consume an AXIS Web Service (running SOAP over HTTP). The Web Service encodes full server-side exception traces in the Soap Fault > Detail element...
3
by: Moshe Kravchik | last post by:
Hi! We have a Web Service written in ATL Server and a client written in Java using Axis. When something goes wrong on the server side, it returns an HRESULT of the error which is translated into...
3
by: nkrisraj | last post by:
Hi, I have a following structure: typedef struct { RateData rdr; int RateID; char RateBalance; } RateInfo;
0
by: relaxedrob | last post by:
Hi All, I have a portType such as this: <portType name="CMLeJobSoapGetEmpBrand"> <operation name="EJobGetEmpBrand"> <input message="tns:EJobEmpBrdReq" name="EJobEmpBrdReq"/> <output...
7
by: priyanka | last post by:
Hi there, I am trying to compare the two strings but I get segmentation fault. const char *function_name; if(strcmp(function_name,"TimerM$HandleFire")==0) The above code gets compiled,...
7
by: pycraze | last post by:
I would like to ask a question. How do one handle the exception due to Segmentation fault due to Python ? Our bit operations and arithmetic manipulations are written in C and to some of our...
3
by: madunix | last post by:
My Server is suffering bad lag (High Utlization) I am running on that server Oracle10g with apache_1.3.35/ php-4.4.2 Web visitors retrieve data from the web by php calls through oci cobnnection...
0
by: Equinex | last post by:
Hi, I am trying to call a Web Service using Php and Soap. Why does the following Php 5 code return? try { //$ExchangeLoginResult = $ExchangeClient->Login(array("request" =>
3
by: =?Utf-8?B?TWFucHJlZXQgU3VzaGls?= | last post by:
I am having a Webservice within which i am throwing SOAP Exceptions and therefore whenever something wrong happens a SOAP fault comes up in the response - see below: <?xml version="1.0"...
0
by: DolphinDB | last post by:
The formulas of 101 quantitative trading alphas used by WorldQuant were presented in the paper 101 Formulaic Alphas. However, some formulas are complex, leading to challenges in calculation. Take...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
0
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.