Re: Spurious segv's and malloc catastrophe


Thanks Paul! That was very helpful indeed!

You were quite correct: crt0_r.o is a symlink to crt0.o. And, I spent
most of today playing around with the malloc debug allocator ... and
actually managed to capture a core dump, although I haven't figured
out anything from it yet. It's been many years since I've worked with
AIX and debugging a core dump is somewhat intimidating!

Am I right in the following assumption: if I shut down every instance
of the particular application, shouldn't the allocated heap be
released, unless it is a shared memory segment or data segments
associated with a shared library held open by some other app? I ask
this, because I have tracked down the most likely culprit to a
particular shared library, which is linked both to the client app as
well as the server app. Even after shutting down all client apps, the
problem continued after restarting the executable. But once I shut
down the server, and released the shared library (as verified with
genkld), the problem disappeared.

I am somewhat at a loss at how to proceed. The shared library is part
of a proprietary commercial software package. Right now, I'm hoping
for some inspiration, or a lucky break!

Thanks again for your input.

Regards,

Jim

.

Relevant Pages

  • Deploying client and server apps
    ... Client Package: ... Common assembly containing the MarshalByRef classes ... I install and run the server app, ... I install the client app, but when I run it I get the error message "Cannot ...
    (microsoft.public.dotnet.framework.remoting)
  • Socket communications through NTLM proxy
    ... wraps many TCP sockets functionalities, ... connect a client app to a server app using port 443. ... I want this setup to work through a NTLM authentication proxy. ...
    (comp.lang.pascal.delphi.misc)
  • Cant access remote server
    ... hope someone has come across this in .NET remoting. ... on the other a server app. ... both machines I am running ZoneAlarm as the firewall and Norton ... place server2 on the same box as the client app and server1 app it ...
    (microsoft.public.dotnet.framework)
  • RE: Sockets work sometimes, sometimes not
    ... If I cancel the client app (which closes and deletes the socket) and then cancel the server app, when I start the server app and then the client app again and try to connect, it won't work. ...
    (microsoft.public.vc.mfc)