headers
Igor Pokrovsky | 1 Apr 2004 04:53

Re: Determining a program's shared libraries at runtime

On Wed, Mar 31, 2004 at 02:55:47PM -0500, Mike Heffner wrote:
> 
> Is there a method in FreeBSD for a program to retrieve the current list of
> dynamic shared libraries it is linked against or has dlopen()'d?

Looks like ldd is doing exactly what you want, take a look at it's sources.

-ip

--

-- 
It's always darkest just before the lights go out.
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Ajit Anand | 1 Apr 2004 06:24

Re: Frequent crashes on 4.9STABLE

On Wed, 31 Mar 2004 19:50:48 +0200, Andre Oppermann <andre <at> freebsd.org> 
wrote:

>
> Very strange.  It crashes when trying to find out whether the packet is 
> for
> an IP address configure on the box itself.  Did you change any compiler
> settings when compiling this kernel?  Maybe -O2 or such?
>
No compiler settings were changed. Only changes made to the GENERIC kernel 
were adding of Firewall options and Debug options.

Rgds,

--

-- 
Ajit Anand
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Mike Heffner | 1 Apr 2004 07:28
Picon
Favicon

Re: Determining a program's shared libraries at runtime


On 01-Apr-2004 Igor Pokrovsky wrote:
| On Wed, Mar 31, 2004 at 02:55:47PM -0500, Mike Heffner wrote:
|> 
|> Is there a method in FreeBSD for a program to retrieve the current list
|> of
|> dynamic shared libraries it is linked against or has dlopen()'d?
| 
| Looks like ldd is doing exactly what you want, take a look at it's
| sources.
| 

Hello, thanks for the response.

The problem I found with ldd was it would only give me the shared objects
linked in at runtime and I needed the list of dlopen()'d objects as well.
On Linux I was able to grab a reference to the link_map list and iterated
through that. Matthew George on the list pointed me to dlinfo(3) which can
return a reference into the link_map list. From my tests this appears to
contain all dlopen()'d libraries as well (also the executable itself,
btw). It also appears to be cleaner than the hack I'm using in Linux to get
the same reference. ;-)

Cheers,

Mike

--

-- 
  Mike Heffner       <mheffner <at> [acm.]vt.edu>
                         <mikeh <at> FreeBSD.org>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Edwin Groothuis | 1 Apr 2004 07:34
Favicon

Re: ld can't find libraries

On Wed, Mar 31, 2004 at 10:12:23PM +0000, Richard Bradley wrote:
> I can't get ld to recognise some "so" libraries without using the -L option:

Ldconfig is used for run-time loading of shared libraries.
What you are doing here is the compilation (linking...) of the
source to a executable.

gcc (ld...) searches by default only for a couple of standard system
directories (/usr/lib for example) and that's all.

If it would search through other directories by default (for example
/usr/local/lib), and your program was trying to link to a newer
version of a library which is in a non-standard directory with an
old one which was in /usr/local/lib, the program would never be
able to get linked to the right one.

Therefor, at compile (link...) time you have to specify explicitely
in which order to search through which directories.

For run-time loading you can use ldconfig or LD_LIBRARY_PATH to
specify where your libraries are.

Edwin
--

-- 
Edwin Groothuis      |            Personal website: http://www.mavetju.org
edwin <at> mavetju.org    |          Weblog: http://weblog.barnet.com.au/edwin/
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel O'Connor | 1 Apr 2004 07:56
Picon
Favicon

UT2004?

Has anyone got it installed under FreeBSD?
I got the demo to run and install pretty well (for some reason I can't play it 
in KDE, I have to drop back to twm otherwise my system hangs), but the full 
game doesn't install :(

I have tried both the DVD edition and the 6 CD version.. It doesn't appear to 
detect that I have mounted a new disk and so I can't get past installing the 
first disks worth of stuff.

I run the installer like so 
sudo /compat/linux/bin/sh /cdrom/linux-installer.sh

and pick /usr/local/ut2004 as the place to install it.

I have ktrace'd it and when I click 'Yes' on the CDROM prompt it only seems to 
try and open fstab and mtab. It ends up with a FreeBSD fstab 
and /compat/linux/etc/mtab which is a zero length file.

I've tried mounting the play disk on /cdrom and /mnt/cdrom, I have also tried 
mounting the DVD on there, and nullfs mounting each of the CD subdirectories 
onto both /cdrom and /mnt/cdrom but no change in behaviour.

I think I'll try copying the Windows install over and unpacking the Linux 
binaries and see how that goes :)

--

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
(Continue reading)

Permalink | Reply | 9 comments |
headers
Kris Kennaway | 1 Apr 2004 08:14

Re: UT2004?

On Thu, Apr 01, 2004 at 03:26:27PM +0930, Daniel O'Connor wrote:
> Has anyone got it installed under FreeBSD?
> I got the demo to run and install pretty well (for some reason I can't play it 
> in KDE, I have to drop back to twm otherwise my system hangs), but the full 
> game doesn't install :(
> 
> I have tried both the DVD edition and the 6 CD version.. It doesn't appear to 
> detect that I have mounted a new disk and so I can't get past installing the 
> first disks worth of stuff.
> 
> I run the installer like so 
> sudo /compat/linux/bin/sh /cdrom/linux-installer.sh
> 
> and pick /usr/local/ut2004 as the place to install it.
> 
> I have ktrace'd it and when I click 'Yes' on the CDROM prompt it only seems to 
> try and open fstab and mtab. It ends up with a FreeBSD fstab 
> and /compat/linux/etc/mtab which is a zero length file.

Is it expecting /compat/linux/etc/mtab to be updated somehow when you
mount the new disk?

Kris
Permalink | Reply | 7 comments |
headers
Daniel O'Connor | 1 Apr 2004 08:17
Picon
Favicon

Re: UT2004?

On Thu, 1 Apr 2004 15:44, Kris Kennaway wrote:
> > I have ktrace'd it and when I click 'Yes' on the CDROM prompt it only
> > seems to try and open fstab and mtab. It ends up with a FreeBSD fstab
> > and /compat/linux/etc/mtab which is a zero length file.
>
> Is it expecting /compat/linux/etc/mtab to be updated somehow when you
> mount the new disk?

That's the implication I guess :)

I fiddled briefly with trying to put stuff in there but I didn't really know 
what the format of it was on a modern linux distro..

Should ask some of my Linux friends I guess..

--

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 9A8C 569F 685A D928 5140  AE4B 319B 41F4 5D17 FDD5
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Mike Silbersack | 1 Apr 2004 08:47

Re: UT2004?


On Thu, 1 Apr 2004, Daniel O'Connor wrote:

> Has anyone got it installed under FreeBSD?
> I got the demo to run and install pretty well (for some reason I can't play it
> in KDE, I have to drop back to twm otherwise my system hangs), but the full
> game doesn't install :(

I only have it running under Windows, but based on my experiences with it,
I recommend that you stop trying to get it installed.  The game is way too
much fun, and will waste all of your precious development time. :)

Mike "Silby" Silbersack
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Bjoern A. Zeeb | 1 Apr 2004 09:10

implications of SMP kernel on UP

Hi,

what are the implications on running an SMP enabled kernel on a UP
machine ?

I first thought of things like:
- performence (most likely not worth the discussion ?)
- additional locking problematic ?
- ... ?

Or asked the other way round: why would I want to disable SMP on a
kernel that is going to run on a UP machine ?

--

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 4 comments |
headers
Helge Oldach | 1 Apr 2004 09:34

Re: FAST_IPSEC bug fix

Julian Elischer:
>On Wed, 31 Mar 2004, Helge Oldach wrote:
>> Mike Tancsa:
>> >Well, its not totally a bug, but missing functionality that looks      
>> >like is there but is not and is pretty important to keep lossy         
>> >links functioning with IPSEC. My colleague gabor <at> sentex.net created    
>> >the patch below that implements net.key.prefered_oldsa when using      
>> >FAST_IPSEC.                                                            
>> 
>> Yep, this is particularly important when running IPSec against other
>> vendors' IPSec implementation. Many appear to prefer the new SA over the
>> old one.
>
>Of course.. If you prefer the old SA over teh new one and your peer is
>rebooted, then you can't talk to them until the old SA expires..

Actually you don't even need to reboot. The issue pops up already when a
new SA is negotiated, but one of the peers insists in using the old one
and the other insists on the new one. Yes, it *should* work in theory,
but often it doesn't. Seen with FreeBSD against Cisco devices, for
instance.

Helge
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |

Gmane