search for: longint

Hi In my R package, imagine I have a C function defined: ?? void myfunc(int *x) { ????? // some code ?? } but when I call it, I pass it a pointer to a longint instead of a pointer to an int. Could this practice potentially result in a segfault? Regards Ben

....duncan at gmail.com> wrote: > >> On 15/08/2018 7:08 AM, Benjamin Tyner wrote: >> Hi >> In my R package, imagine I have a C function defined: >> void myfunc(int *x) { >> // some code >> } >> but when I call it, I pass it a pointer to a longint instead of a >> pointer to an int. Could this practice potentially result in a segfault? > > I don't think the passing would cause a segfault, but "some code" might be expecting a positive number, and due to the type error you could pass in a positive longint and have it...

Thanks for the replies and for confirming my suspicion. Interestingly, src/include/S.h uses a trick: ?? #define longint int and so does the nlme package (within src/init.c). On 08/15/2018 02:47 PM, Herv? Pag?s wrote: > No segfault but a BIG warning from the compiler. That's because > dereferencing the pointer inside your myfunc() function will > produce an int that is not predictable i.e. it is syste...

...t;> >>> On 15/08/2018 7:08 AM, Benjamin Tyner wrote: >>> Hi >>> In my R package, imagine I have a C function defined: >>> void myfunc(int *x) { >>> // some code >>> } >>> but when I call it, I pass it a pointer to a longint instead of a >>> pointer to an int. Could this practice potentially result in a segfault? >> >> I don't think the passing would cause a segfault, but "some code" might be expecting a positive number, and due to the type error you could pass in a positive longint a...

On 15 August 2018 at 20:32, Benjamin Tyner wrote: | Thanks for the replies and for confirming my suspicion. | | Interestingly, src/include/S.h uses a trick: | | ?? #define longint int | | and so does the nlme package (within src/init.c). As Bill Dunlap already told you, this is a) ancient and b) was concerned with the int as 16 bit to 32 bit transition period. Ie a long time ago. Old C programmers remember. You should preferably not even use 'long int' on the othe...

...?s wrote: > On 08/16/2018 05:12 AM, Dirk Eddelbuettel wrote: >> >> On 15 August 2018 at 20:32, Benjamin Tyner wrote: >> | Thanks for the replies and for confirming my suspicion. >> | >> | Interestingly, src/include/S.h uses a trick: >> | >> |? ?? #define longint int >> | >> | and so does the nlme package (within src/init.c). >> >> As Bill Dunlap already told you, this is a) ancient and b) was >> concerned with >> the int as 16 bit to 32 bit transition period. Ie a long time ago. Old C >> programmers remember. >...

On 08/16/2018 05:12 AM, Dirk Eddelbuettel wrote: > > On 15 August 2018 at 20:32, Benjamin Tyner wrote: > | Thanks for the replies and for confirming my suspicion. > | > | Interestingly, src/include/S.h uses a trick: > | > | ?? #define longint int > | > | and so does the nlme package (within src/init.c). > > As Bill Dunlap already told you, this is a) ancient and b) was concerned with > the int as 16 bit to 32 bit transition period. Ie a long time ago. Old C > programmers remember. > > You should preferably not...

FYI, looks like support for Racoon is ending. Does anyone have any experience with the version in ipsec-tools ? ---Mike >Racoon users, > >This is the announcement that the kame project will quit providing >a key management daemon, the racoon, and that "ipsec-tools" will become >the formal team to release the racoon. >The final release of the racoon in the

...y hints about where to look to solve this problem would be much appreciated. Robin Cowan Here is the simple Pascal code: Running on a Macintosh Intel, OS X 10.5, R 2.9.1 {$MODE DELPHI} library LearningLib; const num=75; type array1= array[1..2,1..num] of Double; array2=array[1..num,1..num] of longint; array3=array[1..num,1..num] of Double; array4=array[1..num] of longint; pA1=^array1; pA2=^array2; pA3=^array3; pA4=^array4; pD=^Double; procedure learning(loc1:pA1;adj1:pA2;alpha:pD); cdecl; var i1,i2,neighs:longint; sum1,sum2:double; newloc: array [1..2,1..num] of double; begin for i1:=1 to 2 do...

...months for the University of Cincinnati. We are planning on releasing the project open source when it is more complete. I need to port alot of things to a more general way of doing things and refactor alot of code so this should get better daily. There are some prieview images at my blog http://longint.net/Blog/?p=15 Currently it is just a file browser, it uses ajax has drag and drop and upload with progress the whole bit. The theme other than the banner was done by Ian Monk. other than that i''ve done it all myself. Try it out e-mail me if or when it breaks, i hope you like it. -- Rya...

...s, Berwin ==================== test.c ========================= === compiled via: R SHLIB test.c =================== #define S_Plus #if defined(S_Plus) #include <S.h> #if defined(SPLUS_VERSION) && SPLUS_VERSION >= 4000 # include <newredef.h> #endif #endif static longint *p=NULL; void BT_demo(longint n){ #if defined(S_Plus) if( p != NULL ){ PROBLEM "Possible memory corruption or memory leak.\n We" "advise to restart your S+ session" WARNING(NULL_ENTRY); Free(p); } #endif p = Calloc(n,longint); if (p == NULL){ PROB...

...ors [0000011CH] .chain INTEGER 0 .monitor UpdaterActions.Monitor [01C59510H] BugsCmds.Action.Step [00000BCAH] .a BugsCmds.Action [011D40C0H] .chain INTEGER 0 .i INTEGER 8 .j INTEGER 1000 .numChains INTEGER 1 BugsCmds.Action.Do [00000C58H] .a BugsCmds.Action [011D40C0H] .elapsedTime LONGINT 62EC21F162EB0384H .profileList ARRAY 2024 OF CHAR "" ... .res INTEGER 1635734111 .s ARRAY 120 OF CHAR 3X ... Services.Exec [00000136H] .a Services.Action [011D40C0H] .t POINTER [62EB0384H] Services.IterateOverActions [000002F4H] .p Services.Action [011D40C0H] .t POINTER N...

...CHAR "#Bugs:check" ... .vectorName BOOLEAN FALSE Services.Exec [00000136H] .a Services.Action [011D4F80H] .t POINTER [62AF0170H] Services.IterateOverActions [000002F4H] .p Services.Action [011D4F80H] .t POINTER NIL .time LONGINT 19009968 Services.StdHook.Step [0000034DH] .h Services.StdHook [0101E380H] HostWindows.Idle [00004A86H] .focus BOOLEAN FALSE .tick Controllers.TickMsg Fields .w HostWindows.Window NIL HostMenus.TimerTick [00003422H] .lParam INTEGER 0...

...gsScanners.Scanner Fields .scriptCommand ARRAY 240 OF CHAR "#Bugs:check" ... .vectorName BOOLEAN FALSE Services.Exec [00000136H] .a Services.Action [025B6790H] .t POINTER [64E10170H] Services.IterateOverActions [000002F4H] .p Services.Action [025B6790H] .t POINTER NIL .time LONGINT 4375656 Services.StdHook.Step [0000034DH] .h Services.StdHook [0248E380H] HostWindows.Idle [00004A86H] .focus BOOLEAN FALSE .tick Controllers.TickMsg Fields .w HostWindows.Window NIL HostMenus.TimerTick [00003422H] .lParam INTEGER 0 .ops Controllers.PollOpsMsg Fields .wParam INTEGER...

>>> >>> Those are valid instructions in every x86-32 assembler I'm aware of. >>> Perhaps it needs a switch to put it in 32-bit mode? >> >> Yes, I have been able to confirm that's what's happening behind the >> scene. The switch would be --32, however after that, ld will try to >> link >> the 64-bit versions of libc and the C

I do not know the configury stuff well enough to answer this, can someone else help? On Feb 28, 2008, at 1:55 AM, Joachim Durchholz wrote: > Am Mittwoch, den 27.02.2008, 14:31 -0800 schrieb Dale Johannesen: >> On Feb 27, 2008, at 2:12 PM, Joachim Durchholz wrote: >>> All error messages refer to one of the following four >>> instructions: >>> pushl %ebp