Using dbx to call linked functions

Hi,
We are facing a core dump problem. So please urgently help.
The problem is like this -
the function which is most probably causing the dump is in one of the .o files linked to the main program. The main program is successfully alling the function in lonked file. Using dbx how do I stop in the function in the linked object file?
Please help urgently.
Regards,
Gurudatta

If I understand your question correctly, the dbx command you need to us is stop in
Example
dbx myprog
Reading myprog
(dbx) stop in init_matrix
(2) stop in init_matrix
(dbx) run
(process id 13127)
stopped in init_matrix at line 61 in file "myprog.f"
61 DO 20, I = 1, N
(dbx)
If you have compiled your application with -g then you will be able to view the source within dbx.

Similar Messages

How to implement a callback function using LabView's Call Library Function Node?

I am trying to call a fuction from a SDK.dll library using the Call Library Function Node. The SDK was provided to
me and I do not have the source code, just the .dll and .h files.
The SdkSetPropertyEventHandler function has a callback fuction as one of its parameters. How do I implement the
callback using the CLF node? I am a good LabView programmer but this is my first time using the Call Library
Function Node. I have read all the info I can find on NI's web site and the discussion board but cannot figure
this one out. I am using LabView 8.6.
The SDK.h deacribes the function as:
// Function:   SdkSetPropertyEventHandler
SdkError SDKAPI SdkSetPropertyEventHandler(
            SdkCameraRef                    inCameraRef,
            SdkPropertyEvent                inEvnet,
            SdkPropertyEventHandler         inPropertyEventHandler,
            SdkVoid*                        inContext );
// Description:
//       Registers a callback function for receiving status
//          change notification events for property states on a camera.
// Parameters:
//       In:    inCameraRef - Designate the camera object.
//              inEvent - Designate one or all events to be supplemented.
//              inPropertyEventHandler - Designate the pointer to the callback
//                      function for receiving property-related camera events.
//              inContext - Designate application information to be passed by
//                      means of the callback function. Any data needed for
//                      your application can be passed.
//      Out:    None
// Returns:    Any of the sdk errors.
A separate header file called SDKTypes.h contains the following data:
typedef SdkUInt32 SdkPropertyEvent;
typedef SdkUInt32 SdkPropertyID;
typedef void       SdkVoid;
typedef struct __SdkObject*    SdkBaseRef;
typedef SdkBaseRef    SdkCameraRef;
SdkPropertyEventHandler
typedef SdkError ( SDKCALLBACK *SdkPropertyEventHandler )(
                    SdkPropertyEvent        inEvent,
                    SdkPropertyID           inPropertyID,
                    SdkUInt32               inParam,
                    SdkVoid *               inContext );
Thanks for your help.
Alejandro
Solved!
Go to Solution.

alejandroandreatta wrote:
I am trying to call a fuction from a SDK.dll library using the Call Library Function Node. The SDK was provided to
me and I do not have the source code, just the .dll and .h files.
The SdkSetPropertyEventHandler function has a callback fuction as one of its parameters. How do I implement the
callback using the CLF node? I am a good LabView programmer but this is my first time using the Call Library
Function Node. I have read all the info I can find on NI's web site and the discussion board but cannot figure
this one out. I am using LabView 8.6.
Basically you do not do that. LabVIEW does not know pointers and certainly not function pointers. What you should do instead is writing a C DLL that implements the callback and also exports a function to be called by LabVIEW that translates between the callback and a LabVIEW user event. Look for PostLVUserEvent() here on the NI site to find examples how to do that.
Rolf Kalbermatter
Message Edited by rolfk on 02-11-2009 08:00 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

USING DISTINCT IN CALLING A FUNCTION

Hi to everybody,
I have a problem using DISTINCT in a query where I call a function.
Select
TRACKING_ERROR
rtrim(fs.match),
distinct fb.benchid, ------>>here I want to use distinct
'31.01.1997',
'31.12.1999'
from fondsstamm fs,fondsbench fb
I become an error at the line where distinct fb.benchid is :
literal is missing or in german AUSDRUCK FEHLT.
Can somebody help me??
thanxxx
Schoeib

You cannot have a distinct on just one field. But a work around might be
select TRACKING_ERROR( rtrim(FS.match), A.benchid, '31.01.1997','31.12.1999')
from Fondsstmm FS, (select distinct(benchid) BENCHID from Fondsbench ) A
Hi to everybody,
I have a problem using DISTINCT in a query where I call a function.
Select
TRACKING_ERROR
rtrim(fs.match),
distinct fb.benchid, ------>>here I want to use distinct
'31.01.1997',
'31.12.1999'
from fondsstamm fs,fondsbench fb
I become an error at the line where distinct fb.benchid is :
literal is missing or in german AUSDRUCK FEHLT.
Can somebody help me??
thanxxx
Schoeib

Have anyone used Labview to call MSP430_Memory function in the MSP430.dll?

Hi,
I am trying to read data from Infromation Memory of a MSP430 MCU. I am using MPS-FET430UIF to communicate with the MCU and having trouble to get data using the function MSP430_Memory. Have anyone done this before? I greatly appreciate any help from this forum.

Good Afternoon,
I just have a couple of quick questions for you:
How are you going about calling the dll in LabVIEW?
Are you using the call library function node?
Could you post your code so we can take a look at it and get a better idea how you are going about it?
I hope you have a great rest of the day!
-Cody C

Using variants in Call Library Function Node parameters

Can I use Call Library Function Node to send variant data?
Attached is a VI. Here's the C code:
int MM_FUNC mmDaqDll_407DB
    ( IN char *pcUdlPath
    , IN char *pcTableName
    , IN void *pvData
    int nStat = 1;
    //System:bject *varData = ((System:bject *)vData);
    MessageBox(NULL, pcUdlPath, pcTableName, 0);
    return nStat;
} // mmDaqDll_407DB()
I get the void pointer. I was hoping for a solution that did not use void*.
What is the best way to pass void data to a DLL?
Attachments:
DaqDllMon407DB.vi ‏18 KB

Hi Mefitzpatrick,
Here is a similar forum that addresses this issue:
http://forums.ni.com/ni/board/message?board.id=170&message.id=48886&requireLogin=False
They mention using the Adapt to Type property of the function node inputs, have you tried this?
Let me know if this doesn't answer your question.
Sappster

When using the FILE SEND LINK function, why does the system launch a new window if the email app is already open and active?

I normally have my Yahoo! and Gmail e-mail accounts open and logged into the entire time my system is on. Using your instructions, I have set theFireFox 'mailto' option to USE GMAIL.

Seems Gmail automatically logged me out. When I logged back in and tried again, it still opened a new window, but used my open account to process the e-mail.
Must it always open a new window (which then needs to be closed) in executing this function?

ABAP Calling JAVA Function or Method

Hi Friend,
I need help in how to proceed using ABAP and Call JAVA Function . I know that we need to use RFC enabled Function modules. I was able to connect using JAVA Connector which was provided by SAP For communicating with JAVA Apps. The approach for connecting the JAVA to SAP is working fine. But I have browsed through various website but failed to find any information.Now i am looking forward to help from you friends to solve my problems .
The Requirement is mentioned below:-
1. Prerequiste for SAP ABAP calling a third Party software which is working in JAVA Platform (like any middle ware which might be hardware or software).
2. Sample Code like calling a Text ' Hello to the world calling JAVA from ABAP'.
3. Steps and process so that it would be helpful.
Timely help would be appreciated.
Rajiv Christopher.

1.Middleware is JCO RFC provider it comes with SAP so no need any third party Adapter.
2.
" The ECHOTXT parameter should contain the text of REQUTXT.Information on
" calling the function module should be returned in RESPTXT, indicating, for
" example, in which system and when the function module call was processed.
data:ECHOTEXT type SY-LISEL,
     RESPTEXT type SY-LISEL.
CALL FUNCTION 'STFC_CONNECTION' DESTINATION '<Your JCO destination name>' " which one you have developed in SM59 as TCP/IP
EXPORTING
    requtext       = 'ABAP Calls JAVA'
IMPORTING
   ECHOTEXT       = ECHOTEXT
   RESPTEXT       = RESPTEXT.
if sy-subrc = 0.
WRITE:/'---------------------------------------------------------------------'.
WRITE: / 'establish a link to the ABAP application server with logon data'.
WRITE:/'---------------------------------------------------------------------'.
write:/ ECHOTEXT .
else.
      WRITE:/'---------------------------------------------------------------------'.
WRITE: / 'Not establish a link to the ABAP application server with logon data'.
WRITE:/'---------------------------------------------------------------------'.
endif.
Check the sample code and Let me know will you get ECHOTEXT ?
Kanagaraja L
Edited by: Kanagaraja Lokanathan on Jan 6, 2010 1:27 PM

Call Java functions in a C DLL

Hi,
I am develop a dynamic link library in C on AIX that will internally call java functions using JNI. This libaray will be finally used by other C Executable.
There is only one function in C code i.e. Connect. This function internally use JNI and call java functions. Now while compiling I am facing problems. I think that there is some problem with my makefile.
The make file is given hereunder:
JAVA_HOME = /usr/java14
JAVA_INC = $(JAVA_HOME)/include
CC = cc
LD = cc
# Flags to create a dynamic library.
DYNLINKFLAGS = -G -ostdlib -bnoentry -bM:SRE -brtl -bE:Interface.exp
# files removal
RM = rm -f
#------------------------------------- Libs -----------------------------------#
JAVALIBS      = -L$(JAVA_HOME)/jre/bin/classic/
LIBS            = -ljvm -lpthread -lxnet -lnsl -lm -ldl
#-------------------------------- Dependency rules---------------------------#
# shared library files
LIB_FILES = Interface.a
#-------------------------------------OBJs-------------------------------------#
# shared libraries object files
LIB_OBJS    = Interface.o
all: $(LIB_FILES)
# create our librarys
Interface.a: Interface.o
     $(LD) $(DYNLINKFLAGS) $(JAVALIBS) $(LIBS) $(LIB_OBJS) -o $@
# compile C source files into object files.
%.o: %.c
     $(CC) $(DYNLINKFLAGS) -L$(JAVA_INC) -c $<
# clean everything
clean:
     $(RM) $(LIB_OBJS) $(LIB_FILES)
# clean the library's object files only
cleanlibobjs:
     $(RM) $(LIB_OBJS)Now the problem is that the size of the Interface.a file is very small only 552 bytes. whereas the size of Interface.o file is 34428. Which clearly indicates that the problem is with the Interface.a file i.e during linking.
Can any body help me to figure out the problem.
Regards,
Ahmad Jalil Qarshi

I guess, you are better off to ask this question in a C forum. This is a Java forum, you know.

Trying to call a function from a variable in Flex 4.0 ActionScript and need some suggestions

I am attempting to build a site map in Flex. I have my links (or will have) in a database, along with a "link." On click from a datagrid, I have an event handler where I can get the link. However, everything I have tried to use won't call the function. Ideally, I would like to call a function from from my topLevel application, and I can do that using the mx.core.FlexGlobals.topLevelApplication call. Can anyone point a fairly new Flex coder in the right direction? Thank you.

Here is the function on the group component (simplified): -- I got this from one of my google searches. The other was using the SWFLoader, but since this is in the same application, I didn't think it was as relevant. Plus, the SWFLoader used some references that I couldn't resolve.
private function site_click(event:ListEvent):void {
var sURL:String=list.dataProvider[event.rowIndex].link;
var sCommand:String="mx.core.FlexGlobals.topLevelApplication." + sURL;
this.[sCommand]();
This yields the error message ReferenceError: Error #1059: Property mx.core.FlexGlobals.topLevelApplication.myths_click() not found on sitemap and there is no default value.
Whereas this works fine:
mx.core.FlexGlobals.topLevelApplication.myths_click();
sitemap is my component name.

Call Library Function (DLL) Node Configuration

This issue was discussed few times on this forum (see for example http://forums.ni.com/ni/board/message?board.id=170&message.id=182911 ), but I still have a problem.
My question is - how to define the call to DLL without to specify its full path in order to be able to change the directory path without to change all calls to DLL functions within VI.
So, I did:
1. I put my DLL and my VI in the same directory.
2. I defined this directory in VI search path. This directory also defined as enviroment variable.
3. I use only one call to DLL in this specific VI (just as example in order to simplify the problem).
4. I define only DLL name without the path in CLF Node.
But, every time when I close CLF Node configution window, the program search for the DLL, find it and put full DLL path inside.
I will be very thankful if anyone can help me to overcome this problem.
Best regards,
Boris

Hello Boris,
To sum up the previous posts, when you specify the DLL when configuring the Call Library Function
node, internally LabVIEW stores in the VI either 1) the name of the
DLL, or 2) a relative path from the VI to the DLL (including the name
of the DLL). What's displayed in the dialog (in 'Library Name or Path'
field) is either 1) the name of the DLL, or 2) an absolute path that is
formed by appending the DLL's relative path to the VI's absolute path.
In
case 1, LabVIEW uses the Windows system search paths to load the DLL.
That is, it looks for the DLL in \windows\system32 folder, then if not
found there, it uses the folders specified in the PATH environment
variable, etc.
In case 2, LabVIEW tries to load the DLL from the
computed absolute path (VIs current path combined with the relative
path to the DLL that LabVIEW stored internally). And if not found
there, LabVIEW uses the VI Search Path (that can be set from Tools »
Options in the category of Paths).
So even though LabVIEW automatically puts an absolute path to the DLL
in the Call Library Function Node, as long as you will specify the
correct folder for the DLL in the VI Search Path, you should be Ok. However, if you want to
have a fixed location for the DLL, then it is best to keep it in the
\windows\system32 folder, and specify just the name of the DLL when
configuring the Load Library Function node (this way LabVIEW will not
automatically turn it into an absolute path).
Also, these knowledge base articles might be helpful:
Why Does My VI Prompt for My DLL Every Time I Open It?
LabVIEW Searching for a DLL Used in the Call Library Function Node
My Stand-Alone Executable Cannot Find My DLL, Even Though I Have Specified the Path for the DLL
Hope this helps and good luck with your application!
Shakhina P.
NIC

Calling QuickTime Functions From PowerBuilder

I am using PowerBuilder 9 and would like to call the QuickTime functions from my Windows Vista PC. Has anyone else used PowerBuilder to call these functions?

There have been reported problems with specific compiler versions. Check with oracle as see if there is a specific compiler version number you need for a specific database release.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by krishg:
hi all,
We are trying to call and external C routine (stored in a .so file) from a PL/SQL procedure.
The error obtained is ORA-28576 ( which occurs after connection to the external routine has been established successfully.)
, which states that the problem may lie in:
a) Abnormal Termination of external C routine.(i.e a case of coredump, memory fault etc).
b) Network Problems.
c) Internal Logic Error in the RPC transfer code.
We tried calling the C .so functions from a C executable and it is working fine. Also there doesn't appear to a problem in the network connections too.....
The environment we are working on is Digital Unix 4.0 F. and we are using Oracle 8.0.6
Please advise,
Krishnan<HR></BLOCKQUOTE>
null

How to call external functions without a .DLL (just using a .H and .LIB file)?

Hello everyone,
actually I'm facing little difficulties on how to get an external function getting called from within CVI (Version 2009).
I was supplied with a .H file and a .LIB file to call an external function from within my CVI project. The .H file looks like this:
void exportedFunction(double *parameter);
As far as I know, the external function was written with MS Visual C++ 6.
So I tried to statically link to the extern al function like this:
- Add the .H file and the .LIB file to the CVI project
- #include the .H file where I needed to call the external function
- do the external function call
When building I get an unresolved external function call error from CVI so this seems not to be working.
I made some searches around and got up with two possible issues. Maybe one of you can help me get a bit further and get things working.
1) The "real" function code is located in the DLL file which was not delivered to me. Or is there a way to get things done (call external functions) just with a .H and a .LIB file (without any .DLL file included)?
2) The external function does not export according to "C-Style" rules. The function signature in the .H file shows no things like
extern "C" __declspec(dllexport) void __stdcall ...
Or maybe it's a combination of both issues (missing .DLL + wrong export style of function)?
I guess I could get around the wrong export style of the function when I manage to write a wrapper around the original function that actually uses C-Style exporting. But I guess I need the .DLL file for this try as well.
Thank you for your answers.
Best regards,
Bernd
Solved!
Go to Solution.

There is no need for the dllexport stuff. There is also the option for a static library without any DLL. But the 'extern "C"' is essential, because it forces the C++ compiler, which was probably used to compile the library , to use C calling convention.
If you can't ask the provider of the library to provide a version which was compiled using C calling convention the way to go is to write a wrapper with VC++6 around that library which reexports the functions using C calling convertion. Something like
extern "C" type0 myfunc1(type1 arg1, ...) {
return func1( arg1,...);
for every function , you need to use.
BTW. "unresolved symbol" is the linker error message, you can expect if you try to link C code against a library build with C++ calling convention.

PDA: Calling library functions - seems to link the stubbed .cpp file instead of the DLL

I'm having trouble developing a Lab View PDA module that calls a DLL built using Visual C++. The DLL functions correctly when called in a non-PDA VI. My issues seem to be with porting to the PDA.
My configuration:
- Lab View 8.5 with the PDA 8.5 module
- Visual Studio 8.0 with the Windows Mobile 6.0 SDK
- ASUS 626 PDA with an Intel PXA70 procesor running Windows Mobile 6 Classic
Following the PPCBatt example code provided with the PDA module, I have:
- used extern "C" to prevent name mangling
- placed the DLL built with the Windows Mobile SDK in the \Windows directory on the PDA
- created a stub Win32 DLL and lib
- created a stubbed cpp file whose functions only return zero
- included the stubbed cpp and lib files in the build spec / source files / additional files
- placed Call Library Function nodes on my PDA VI, selected the function names, set the parameter types
- built and deployed the executable, both with and without debug
When I set the library path property of the Call Library Node, the functions appeared in the function name pulldown, but the parameters did not populate. I had to manually add them and set their types. The help page says they would autopopulate when the function was selected.
I've debugged the VI, and the Library Function Call nodes are being called. It seems the build is linking the code from the stub C file provided in the additional files portion of the source files property page, instead of adding hooks to call the DLL on the PDA. As a test, I changed an output parameter in one of the functions in the stubbed cpp file - the changed value showed in the front panel indicator.
What am I doing wrong?
Dan

Hi Dan,
I'm not sure if I understood you problem fully. When calling external code with LabVIEW PDA, the DLL acts as a stub DLL with the correct function prototypes for the C code that you want to call. Here's a Knowledge Base article that might help explain about calling External Code in LabVIEW PDA.
Regards,
Stanley Hu
National Instruments
Applications Engineering
http://www.ni.com/support

Call library function node with array of clusters using array data pointer

Hello all.
I am writing a LabVIEW wrapper for an existing DLL function.
The function has, as one of its parameters, an array of structs. The struct is very simple, containing two integers. I am using the call library function node to access it.
In Labview I created an array of clusters, where the cluster has two 32-bit integers as its members. So far, so good.
Now I have to pass this in to the Call Library Function Node. Here I am running into trouble.
I have used The topic in LAVA and The topic in the knowledge base as my primary sources of information, though I have read a bunch of forum topics on the subject too.
I do understand that I could write a new function which takes as a parameter a struct with the size as the first member and an array as the second, and I might just do this and have it call the regular function, but I was hoping to do it more simply.
According to the C file which LabVIEW generates for me from the CLFN when I choose "Adapt to Type" and "Array Data Pointer", the prototype it is expecting is:
int32_t myFunc(uint32_t handle, uint16_t channel,
int32_t FIFOnumber, void data[], int32_t numWords, int32_t *actualLoaded,
int32_t *actualStartIndex);
And the prototype of the function in my DLL is
int borland_dll myFunc(DWORD handle, usint channel,
int FIFOnumber, struct mStruct *data, int numWords, int *actualLoaded, int *actualStartIndex);
This looks like a match to me, but it doesn't work (I get garbage in data). From the topic in LAVA referenced above, I understood that it would work. It does not.
If I cast data to the pointer-to-pointer I get when I generate c code by wiring my struct to a CIN and generating, then I seem to get what I expect. But this seems to work when I choose "pointers to handles" too, and I would expect array data pointer to give a different result.
Is there any way to get this to work directly, or will I have to create a wrapper? (I am currently using LabVIEW 2011, but we have customers using 2009 and 2012, if not other versions as well).
Thank you.
Batya
Solved!
Go to Solution.

OK, here is more detailed information.
I have attached the VI.
This is the code from the "C" file created by right-clicking the CLN and creating a "C" file.
When the parameter in the CLN is set to "array data pointer":
/* Call Library source file */
#include "extcode.h"
int32_t Load_Transmit_FIFO_RTx(uint32_t handle, uint16_t channel,
int32_t FIFOnumber, void data[], int32_t numWords, int32_t *actualLoaded,
int32_t *actualStartIndex);
int32_t Load_Transmit_FIFO_RTx(uint32_t handle, uint16_t channel,
int32_t FIFOnumber, void data[], int32_t numWords, int32_t *actualLoaded,
int32_t *actualStartIndex)
/* Insert code here */
When the parameter is "pointers to handles":
/* Call Library source file */
#include "extcode.h"
/* lv_prolog.h and lv_epilog.h set up the correct alignment for LabVIEW data. */
#include "lv_prolog.h"
/* Typedefs */
typedef struct {
int32_t control;
int32_t data;
} TD2;
typedef struct {
int32_t dimSize;
TD2 data[1];
} TD1;
typedef TD1 **TD1Hdl;
#include "lv_epilog.h"
int32_t Load_Transmit_FIFO_RTx(uint32_t handle, uint16_t channel,
int32_t FIFOnumber, TD1Hdl *data, int32_t numWords, int32_t *actualLoaded,
int32_t *actualStartIndex);
int32_t Load_Transmit_FIFO_RTx(uint32_t handle, uint16_t channel,
int32_t FIFOnumber, TD1Hdl *data, int32_t numWords, int32_t *actualLoaded,
int32_t *actualStartIndex)
/* Insert code here */
When the parameter is set to "handles by value":
/* Call Library source file */
#include "extcode.h"
/* lv_prolog.h and lv_epilog.h set up the correct alignment for LabVIEW data. */
#include "lv_prolog.h"
/* Typedefs */
typedef struct {
int32_t control;
int32_t data;
} TD2;
typedef struct {
int32_t dimSize;
TD2 data[1];
} TD1;
typedef TD1 **TD1Hdl;
#include "lv_epilog.h"
int32_t Load_Transmit_FIFO_RTx(uint32_t handle, uint16_t channel,
int32_t FIFOnumber, TD1Hdl *data, int32_t numWords, int32_t *actualLoaded,
int32_t *actualStartIndex);
int32_t Load_Transmit_FIFO_RTx(uint32_t handle, uint16_t channel,
int32_t FIFOnumber, TD1Hdl *data, int32_t numWords, int32_t *actualLoaded,
int32_t *actualStartIndex)
/* Insert code here */
As to the DLL function, it is a bit more complicated than I explained above, in the current case. My VI calls the function by this name in one DLL, and that DLL loads a DLL and calls a function (with the same name) in the second DLL, which does the work. (Thanks Rolfk, for helping me with that one some time back!)
Here is the code in the first ("dispatcher") DLL:
int borland_dll Load_Transmit_FIFO_RTx(DWORD handle, usint channel, int FIFOnumber, struct FIFO_DATA_CONTROL *data, int numWords, int *actualLoaded, int *actualStartIndex)
t_DispatchTable *pDispatchTable = (t_DispatchTable *) handle;
int retStat = 0;
retStat = mCheckDispatchTable(pDispatchTable);
if (retStat < 0)
return retStat;
if (pDispatchTable->pLoad_Transmit_FIFO_RTx == NULL)
return edispatchercantfindfunction;
return pDispatchTable->pLoad_Transmit_FIFO_RTx(pDispatchTable->handlertx, channel, FIFOnumber, data, numWords, actualLoaded, actualStartIndex);
borland_dll is just "__declspec(dllexport)"
The current code in the DLL that does the work is:
// TEMP
typedef struct {
int control;
int data;
} TD2;
typedef struct {
int dimSize;
TD2 data[1];
} TD1;
typedef TD1 **TD1Hdl;
// END TEMP
int borland_dll Load_Transmit_FIFO_RTx(int handlertx, usint channel, int FIFOnumber, struct FIFO_DATA_CONTROL *data, int numWords, int *actualLoaded, int *actualStartIndex){
struct TRANSMIT_FIFO *ptxFIFO; //pointer to transmit FIFO structure
usint *pFIFOlist; //pointer to array of FIFO pointers to FIFO structures
int FIFOentry, numLoaded;
usint *lclData;
usint nextEntryToTransmit;
// TEMP
FILE *pFile;
int i;
TD1** ppTD = (TD1**) data;
TD1 *pTD = *ppTD;
pFile = fopen("LoadFIFOLog.txt", "w");
fprintf(pFile, "Starting Load FIFO with %d data words, data pointer 0x%x, with the following data&colon; \n", numWords, data);
for (i = 0; i < numWords; i++) {
fprintf(pFile, "%d: control--0x%x, data--0x%x \n", i, data[i].control, data[i].data);
fflush(pFile);
fprintf(pFile, "OK, using CIN generated structures: dimSize %d, with the following data&colon; \n", pTD->dimSize);
for (i = 0; i < numWords; i++) {
fprintf(pFile, "%d: control--0x%x, data--0x%x \n", i, pTD->data[i].control, pTD->data[i].data);
fflush(pFile);
// END TEMP
if ((handlertx) <0 || (handlertx >= NUMCARDS)) return ebadhandle;
if (cardrtx[handlertx].allocated != 1) return ebadhandle;
pFIFOlist = (usint *) (cardrtx[handlertx].segaddr + cardrtx[handlertx].glob->dpchn[channel].tr_stk_ptr);
pFIFOlist += FIFOnumber;
ptxFIFO = (struct TRANSMIT_FIFO *)(cardrtx[handlertx].segaddr + *pFIFOlist);
//use local copy of ptxFIFO->nextEntryToTransmit to simplify algorithm
nextEntryToTransmit = ptxFIFO->nextEntryToTransmit;
//on entering this routine nextEntryToLoad is set to the entry following the last entry loaded
//this is what we need to load now unless it's at the end of the FIFO in which case we need to wrap around
if ( ptxFIFO->nextEntryToLoad >= ptxFIFO->numEntries)
*actualStartIndex = 0;
else
*actualStartIndex = ptxFIFO->nextEntryToLoad;
//if nextEntryToLoad points to the last entry in the FIFO and nextEntryToTransmit points to the first, the FIFO is full
//also if nextEntryToLoad == nextEntryToTransmit the FIFO is full and we exit without loading anything
if (( (( ptxFIFO->nextEntryToLoad >= ptxFIFO->numEntries) && (nextEntryToTransmit == 0)) ||
( ptxFIFO->nextEntryToLoad == nextEntryToTransmit)) && (ptxFIFO->nextEntryToLoad != INITIAL_ENTRY)){
*actualLoaded = 0; //FIFO is full already, we can't add anything
return 0; //this is not a failure, we just have nothing to do, this is indicated in actualLoaded
numLoaded = 0;
lclData = (usint *)data; //must use 16 bit writes to the module
//conditions are dealt with inside the for loop rather than in the for statement itself
for (FIFOentry = *actualStartIndex; ; FIFOentry++) {
//if we reached the end of the FIFO
//if the module is about to transmit the first element of the FIFO, the FIFO is full and we're done
//OR if the module is about to transmit the element we're about to fill in, we're done - the
//exception is if this is the first element we're filling in which means the FIFO is empty
if ((( FIFOentry >= ptxFIFO->numEntries) && (nextEntryToTransmit == 0)) ||
((FIFOentry == nextEntryToTransmit) && (FIFOentry != *actualStartIndex) )){
*actualLoaded = numLoaded;
//set nextEntryToLoad to the end of the FIFO, we'll set it to the beginning next time
//this allows us to distinguish between full and empty: nextEntryToLoad == nextEntryToTransmit means empty
ptxFIFO->nextEntryToLoad = FIFOentry;
return 0;
//we reached the end but can continue loading from the top of the FIFO
if ( FIFOentry >= ptxFIFO->numEntries)
FIFOentry = 0;
//load the control word
ptxFIFO->FifoData[FIFOentry * 3] = *lclData++;
//skip the high of the control word, the module only has a 16 bit field for control
lclData++;
//now put in the data
ptxFIFO->FifoData[(FIFOentry * 3) + 2] = *lclData++;
ptxFIFO->FifoData[(FIFOentry * 3) + 1] = *lclData++;
numLoaded++;
//we're done because we loaded everything the user asked for
if (numLoaded >= numWords) {
*actualLoaded = numLoaded;
ptxFIFO->nextEntryToLoad = FIFOentry+1;
return 0;
//if we reached here, we're done because the FIFO is full
*actualLoaded = numLoaded;
ptxFIFO->nextEntryToLoad = FIFOentry;
fclose (pFile);
return 0;
As you can see, I added a temporary diagnostic with the structures that were created in the "Handles by value" case, and print out the data. I see what is expected, whichever of the options I pick in the CLN!
I understood (from the information in the two links I mentioned in my original post, and from the name of the option itself) that "array data pointer" should pass the array of data itself, without the dimSize field. But that does not seem to be what is happening.
Batya
Attachments:
ExcM4k Load Transmit FIFO.vi ‏15 KB

Link that calls DB function in report

I have a standard report. I would like to add 2 links to the end of each row with the action by the user.
For example:
Order No Name Action
123 John Doe Approve | Decline
456 Jane Dow Approve | Decline
Where Approve and Decline are links that call DB functions.
How do I begin?
TIA
Scott

Hi Scott,
You can try this
Create an application level item F101_ID
Create 2 appication level processes to call you're stored procedures / functions.
One for Accept and one Decline. F101_ID would probably be the PK of the record you are dealing with or
in the example below "column_name_1"
If you want to use a icon
select .....
'<img src="#WORKSPACE_IMAGES#accept.ico" width="30" height="30" alt="Accept"'
|| 'onclick="javascript:accept(this,'||column_name_1||','||column_name_2||');">',
'<img src="#WORKSPACE_IMAGES#decline.ico" width="30" height="30" alt="Accept"'
|| 'onclick="javascript:decline(this,'||column_name_1||','||column_name_2||');">'
from table_name
if you want to use a URL then use this
select ....
'a href="javascript:accept(this,'||column_name_1||','||column_name_2||');">Accept',
'a href="javascript:decline(this,'||column_name_1||','||column_name_2||');">Decline'
from table_name
On your page definition under HTML header add the following javascript
<script language="JavaScript" type="text/javascript">
function accept(pThis,pSelect,formItem1){
alert("Accepted.");
var l_Return = null;
var url;
var l_Select = html_GetElement(pSelect);
var get = new htmldb_Get(null,$x('pFlowId').value,
'APPLICATION_PROCESS=ACCEPT',0);
get.add('F101_ID',pSelect);
gReturn = get.get('XML');
url = 'f?p=&APP_ID.:108:&APP_SESSION.::::P108_ID:' + formItem1;
w = window.location(url);
return false;
</script>
<script language="JavaScript" type="text/javascript">
function decline(pThis,pSelect,formItem1){
alert("Declined.");
var l_Return = null;
var url;
var l_Select = html_GetElement(pSelect);
var get = new htmldb_Get(null,$x('pFlowId').value,
'APPLICATION_PROCESS=DECLINE',0);
get.add('F101_ID',pSelect);
gReturn = get.get('XML');
url = 'f?p=&APP_ID.:108:&APP_SESSION.::::P108_ID:' + formItem1;
w = window.location(url);
return false;
</script>
Hope this helps
Connor
Edited by: user4505115 on 2010/05/03 1:40 PM
Edited by: user4505115 on 2010/05/03 1:41 PM

Using dbx to call linked functions

Similar Messages

Maybe you are looking for