apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)" <mad...@hp.com>
Subject RE: [PATCH] Be verbose during shl_load on HP-UX
Date Wed, 28 May 2003 22:33:39 GMT
Huh.. In that case, do we use the apr_dso_error to tell the user why the
shl_load failed ?.. Because, I don't see it.. In my case, there were a bunch
of unresolved symbols in some module, and the only error message that I got
in the log file was "unable to load blah blah blah".. 
OTOH, if I enable BIND_VERBOSE, it gives me exactly what was the cause -
unresolved symbol or unable to open a dependent library or something like
that.. I would think that the users would 'prefer' to know whatz happening.

-Madhu

>-----Original Message-----
>From: Joe Orton [mailto:joe@manyfish.co.uk]
>Sent: Wednesday, May 28, 2003 3:10 PM
>To: MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)
>Cc: 'dev@apr.apache.org'
>Subject: Re: [PATCH] Be verbose during shl_load on HP-UX
>
>
>On Wed, May 28, 2003 at 02:46:28PM -0700, 
>MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote:
>> 	'wondering if anybody has objections for the below 
>patch. By having
>> the BIND_VERBOSE option, we can know what really failed 
>during the shl_load.
>
>Hi Madhu, BIND_VERBOSE was removed on purpose - the defined interface
>for retrieving error strings is apr_dso_error() - having one
>implementation also spit errors on fd 2 is both inconsistent and
>generally a bad idea (since the app may close stderr and open something
>else there).
>
>joe
>
>> diff -u -r1.61 dso.c
>> --- dso.c       16 Feb 2003 10:00:08 -0000      1.61
>> +++ dso.c       28 May 2003 21:43:01 -0000
>> @@ -119,7 +119,7 @@
>>                                         const char *path, 
>apr_pool_t *pool)
>>  {
>>  #if defined(DSO_USE_SHL)
>> -    shl_t os_handle = shl_load(path, BIND_IMMEDIATE, 0L);
>> +    shl_t os_handle = shl_load(path, 
>BIND_IMMEDIATE|BIND_VERBOSE, 0L);
>>  
>>  #elif defined(DSO_USE_DYLD)
>>      NSObjectFileImage image;
>

Mime
View raw message