|
Home > Archive > Unix Programming > June 2005 > different between .so and not
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
different between .so and not
|
|
| dt1649651@yahoo.com 2005-06-22, 5:57 pm |
| I have similar apps, under Linux, compiled by gcc, that handle the (
socket ) requests, handle data, process data and reply to the requests.
When processing data, I use a external database API.They all work
normally.
Because of the similarity of these apps in the way of handling
requests, I re-wrote them that each mentioned-above app is compiled as
a .so library, and the main app uses dlopen and dlsym to load functions
of those apps. When there is a request, the main app will check which
app this request wants to work with, and will call the coressponding
module's functions. This is not quite but pretty much similar to the
(x)inetd daemon.
My problem is in this case, the external database library, which is
used by the .so apps, accidentally quits with a fatal error.
So my question is what is the difference in stack/memory... of a
function that is called as a static memory and dynamically-loaded
function ?
Thanks for your advice,
DT
| |
| David Schwartz 2005-06-22, 5:57 pm |
|
<dt1649651@yahoo.com> wrote in message
news:1119468667.180826.241020@g47g2000cwa.googlegroups.com...
> My problem is in this case, the external database library, which is
> used by the .so apps, accidentally quits with a fatal error.
Troubleshoot.
> So my question is what is the difference in stack/memory... of a
> function that is called as a static memory and dynamically-loaded
> function ?
There are many differences, and there's no way to know which of those is
relevent. It may not have anything directly to do with that difference.
Get a core dump and analyze it. Or look at the specific error returned.
DS
|
|
|
|
|