You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Cliff Woolley <jw...@virginia.edu> on 2002/04/19 20:20:04 UTC

Re: cvs commit: httpd-2.0/build instdso.sh

On 19 Apr 2002 trawick@apache.org wrote:

> trawick     02/04/19 07:04:30
>
>   Modified:    .        CHANGES
>                build    instdso.sh
>   Log:
>   Change instdso.sh to use libtool --install everywhere and then
>   clean up some stray files and symlinks that libtool leaves around
>   on some platforms.  This gets subversion building properly since
>   it needed a re-link to be performed by libtool at install time,
>   and the old instdso.sh logic to simply cp the DSO didn't handle
>   that requirement.

I need to experiment with this a bit more, but it looks like it might be
causing my DSO's to be undebuggable.  :( I can't set breakpoints, I can't
even step into the DSOs -- calls through them get skipped right over.
Might libtool --install strip away debugging symbols?

--Cliff

--------------------------------------------------------------
   Cliff Woolley
   cliffwoolley@yahoo.com
   Charlottesville, VA



Re: cvs commit: httpd-2.0/build instdso.sh

Posted by Cliff Woolley <jw...@virginia.edu>.
On Tue, 23 Apr 2002, Greg Ames wrote:

> > Sheesh.  Anyone know how to fix that?
>
> you aren't going to like my fixes...
>
> * use static builds for debugging
> * upgrade the OS

I ended up upgrading gdb from 5.0 to 5.1.1 and building it for i686
instead of i386, and between those two changes, it's fixed for DSOs.
Thanks!

--Cliff

--------------------------------------------------------------
   Cliff Woolley
   cliffwoolley@yahoo.com
   Charlottesville, VA



Re: cvs commit: httpd-2.0/build instdso.sh

Posted by Greg Ames <gr...@apache.org>.
Cliff Woolley wrote:

> However, I guess I should have kept my eyes open to what gdb was telling
> me:
> 
> warning: Unable to find dynamic linker breakpoint function.
> GDB will be unable to debug shared library initializers
> and track explicitly loaded dynamic code.

that sounds familiar
 
> Sheesh.  Anyone know how to fix that?

you aren't going to like my fixes...

* use static builds for debugging
* upgrade the OS

I got the same thing after "upgrading" Linux, maybe to Mandrake 7.2.  I googled
and decided it would be a mess to fix by upgrading individual RPMs.  I believe
it went away after installing Mandrake 8.0.

Greg

Re: cvs commit: httpd-2.0/build instdso.sh

Posted by Cliff Woolley <jw...@virginia.edu>.
On 19 Apr 2002, Jeff Trawick wrote:

> It should be really easy to test your theory.  Just use cp to copy
> your DSO from modules/foo/.libs into the right installed place.

Uggh, that didn't help.  :(  So I guess I can't blame it on you guys.  ;]

However, I guess I should have kept my eyes open to what gdb was telling
me:

warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.

Sheesh.  Anyone know how to fix that?

Thanks,
Cliff

--------------------------------------------------------------
   Cliff Woolley
   cliffwoolley@yahoo.com
   Charlottesville, VA



Re: cvs commit: httpd-2.0/build instdso.sh

Posted by Jeff Trawick <tr...@attglobal.net>.
Cliff Woolley <jw...@virginia.edu> writes:

> On 19 Apr 2002 trawick@apache.org wrote:
> 
> > trawick     02/04/19 07:04:30
> >
> >   Modified:    .        CHANGES
> >                build    instdso.sh
> >   Log:
> >   Change instdso.sh to use libtool --install everywhere and then
> >   clean up some stray files and symlinks that libtool leaves around
> >   on some platforms.  This gets subversion building properly since
> >   it needed a re-link to be performed by libtool at install time,
> >   and the old instdso.sh logic to simply cp the DSO didn't handle
> >   that requirement.
> 
> I need to experiment with this a bit more, but it looks like it might be
> causing my DSO's to be undebuggable.  :( I can't set breakpoints, I can't
> even step into the DSOs -- calls through them get skipped right over.
> Might libtool --install strip away debugging symbols?

It should be really easy to test your theory.  Just use cp to copy
your DSO from modules/foo/.libs into the right installed place.

More massive suckage (but let's hope it wasn't instdso.sh or
libtool)...

-- 
Jeff Trawick | trawick@attglobal.net
Born in Roswell... married an alien...

RE: cvs commit: httpd-2.0/build instdso.sh

Posted by Sander Striker <st...@apache.org>.
> From: Cliff Woolley [mailto:jwoolley@virginia.edu]
> Sent: 19 April 2002 20:20

> On 19 Apr 2002 trawick@apache.org wrote:
> 
> > trawick     02/04/19 07:04:30
> >
> >   Modified:    .        CHANGES
> >                build    instdso.sh
> >   Log:
> >   Change instdso.sh to use libtool --install everywhere and then
> >   clean up some stray files and symlinks that libtool leaves around
> >   on some platforms.  This gets subversion building properly since
> >   it needed a re-link to be performed by libtool at install time,
> >   and the old instdso.sh logic to simply cp the DSO didn't handle
> >   that requirement.
> 
> I need to experiment with this a bit more, but it looks like it might be
> causing my DSO's to be undebuggable.  :( I can't set breakpoints, I can't
> even step into the DSOs -- calls through them get skipped right over.
> Might libtool --install strip away debugging symbols?

It might, but I surely hope not.  And I don't think it does.
How would people debug libtool installed libs otherwise?
 
> --Cliff

Sander