On 26.06.2011 23:00, Mark Miesfeld wrote:
> On Sun, Jun 26, 2011 at 6:06 AM, Rony G. Flatscher
> wrote:
>
>
>> while developing an external funciton library for 64-bit ooRexx (using
>> 4.1.0) on a 64-bit Linux machine, all of a sudden I have been getting
>> segmentation faults in a code segment that contains no Rexx-API code. The
>> native code does not itself use glibc's realloc().
>>
> If you pass a bad pointer down into someone else's library, that could
> cause what you are seeing. Whether you use realloc or not.
>
> I would google "dbus realloc problem" There are a lot of hits. I
> didn't look at any of them, but it is possible they could give you a
> hint.
>
O.K., will look back into this (have a certain combination of calls
induced by testscripts that surface these problems) later, once I have
finished the library and have it tested by a student over the summer. If
I find the reason myself, I will come back to report it.
---rony
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
