© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
What we have is OK. Scanning the path is error prone. Earlier versions of Windows supply the full executable name as argv[0] which works fine. Later versions, including Windows 7, use the user command name instead.
We could change libiberty to pull the module filename but it's not needed.