segv on lookup?
Fairlight
fairlite at fairlite.com
Thu Aug 8 13:14:06 PDT 2013
I'm at a loss as to what's going on here. I haven't had any troubles with
a CALLed table until now, when it's being called by a different calling
table. Suddenly, it wants to segv without fail.
Here's the lookup in the called table:
lookup pstn = pevent k=(ValKey) i=A -npx
That's what's segfaulting.
The calling table is sitting on a record in a file that's just used as
"slots" to sit on while doing all work via lookups. There's a lookup
currently active on the pevent table at the time of segv, but it's
non-protected. This is the active lookup in question:
lookup pstat = pevent r=(ValKey) -n
Any clues? The called table works flawlessly outside of this context, when
I'm just sitting in dreport on a record that has nothing to do with the
pevent file. The only time I'm running into trouble seems to be in this
new calling table, which has a greater-than lookup via an @rn index,
cycling through all records and looking for the ones to process in a
getnext loop.
I'm not even sure that the two lookups are colliding to cause the segv or
not, honestly. It's my primary guess, since it's the main difference.
filePro for Linux, 5.0.14R4
mark->
--
Fairlight Consulting
http://www.fairlite.com
fairlite at fairlite.com
(502) 509-3840
More information about the Filepro-list
mailing list