topic Re: strtok_r 64 BIT HP unix in Operating System - HP-UX

strtok_r 64 BIT HP unix

Srinivasan S_1 — Tue, 24 Feb 2004 06:28:24 GMT

Is strtok_r is supported in 64 BIT HP unix ?
When compiled in 64 Bit it gives warning.
and on usage it gives core dump.

Have any one faced similar problem ,thought confirm.

Re: strtok_r 64 BIT HP unix

Karthik S S — Tue, 24 Feb 2004 06:32:59 GMT

Did you try this depot file?? Not sure if it will be helpful,

http://hpux.connect.org.uk/hppd/hpux/Development/Tools/TS-1.08/

-Karthik S S

Re: strtok_r 64 BIT HP unix

Mark Grant — Tue, 24 Feb 2004 06:46:40 GMT

Well, I've just been playing with it and strtok() is fine but I get a bus error using strtok_r.

Weird! I'll keep playing with that!

Re: strtok_r 64 BIT HP unix

Mark Grant — Tue, 24 Feb 2004 06:52:38 GMT

Actually, I'm seem to be going a bit daft. Forgot that strtok_r needs to be passed the address of the character string pointer, not the character string pointer itself. It seems to be ok now.

Maybe you are doing the same thing?

Re: strtok_r 64 BIT HP unix

Srinivasan S_1 — Tue, 24 Feb 2004 07:14:48 GMT

Eg: t1.c
#include
#include
#include
void main(){
char usr[36];
char *name[5];
char *arr=NULL;
memset(usr,'\0',sizeof(usr));
strcpy(usr,"ab cd ef");
name[0]=(char *)strtok_r(usr," ",&arr);
printf("arr is %s\n",arr);
printf("name is %s\n",name[0]);
return ;
}
[node:/tmp]
Compilation Trace:
cc +DD64 -g -o t1 t1.c
cc: 487: warning : Possibly incorrect message catalog.
cc: "t1.c", 10: 724: , line : warning Cast: converts default int return type to pointer.

The same Code goes without warning in 32 bit compilation mode but aborts in 64 bit.
I am unable to track why this warning is produced in 64 BIT compilation

Thanks.

Re: strtok_r 64 BIT HP unix

Mark Grant — Tue, 24 Feb 2004 07:28:19 GMT

Ok, I have just compiled and run your code fine on 11.0 64 bit and 11i 64 bit.

What compiler are you using? I'm just using the default compiler that comes with a standard HPUX install. I just compiled it fine using gcc though that was on Linux.

Re: strtok_r 64 BIT HP unix

Srinivasan S_1 — Tue, 24 Feb 2004 07:41:38 GMT

cpp.ansi: HP92453-01 B.11.11.06 HP C Preprocessor (ANSI)
ccom: HP92453-01 B.11.11.28212.GP HP C Compiler

Re: strtok_r 64 BIT HP unix

Srinivasan S_1 — Tue, 24 Feb 2004 07:42:14 GMT

The compiler used for strtok_r problem is

cpp.ansi: HP92453-01 B.11.11.06 HP C Preprocessor (ANSI)
ccom: HP92453-01 B.11.11.28212.GP HP C Compiler

Re: strtok_r 64 BIT HP unix

Mark Grant — Tue, 24 Feb 2004 07:50:48 GMT

I can't see any patches for this either.

If you are running this on a 64 bit machine, try compiling it with no options i.e just "-o"

Re: strtok_r 64 BIT HP unix

Adam J Markiewicz — Tue, 24 Feb 2004 07:55:19 GMT

Hi

>>
cc: "t1.c", 10: 724: , line : warning Cast: converts default int return type to pointer.
<<

Undoubtly you use the function that is not previously declared to the compiler. It should work even without casting.

try:

cc +DD64 -g -o t1 -D_REENTRANT t1.c

Good luck
Adam

Re: strtok_r 64 BIT HP unix

Mark Grant — Tue, 24 Feb 2004 08:00:30 GMT

Adam,

I tried it with and without the cast. Both worked fine though without the cast produced warnings at compile.

Re: strtok_r 64 BIT HP unix

Srinivasan S_1 — Tue, 24 Feb 2004 08:16:58 GMT

Hi !
Its working ! Thanks.

I thought REENTRANT option should be used for Multithreading functions.

Since,strtok_r one way is reentrancy even though no multithreaded calls are there ,we should use this option.

Is my understanding correct.

Thanks for help. But I am not able to understand whether this is justified

Re: strtok_r 64 BIT HP unix

Adam J Markiewicz — Tue, 24 Feb 2004 09:23:34 GMT

Hi

Srinivasan,

I'm glad it's working.
Sometimes analyzing teories is less usefull than simple source checking:

more /usr/include/string.h

[...]

# ifdef _REENTRANT
extern char *strtok_r(char *, const char *, char **);
# ifdef _PTHREADS_DRAFT4
extern int strerror_r(int, char *, int);
# endif /* _PTHREADS_DRAFT4 */
# endif

[...]

And thats it. Not defined = not declared.

Mark,

I'm surprized that it produced warnings, as return value is char * and is assigned to char *, so I cannot see what to warn about. However I have a rule not to argue with facts.

Good luck
Adam