[haiku-development] Re: Undefined reference to __toupper_l.

Stephan Assmus wrote:

Bruno Albuquerque wrote (2008-01-31, 14:38:57 [+0100]):

Stephan Assmus wrote:

Bruno Albuquerque wrote (2008-01-31, 13:40:36 [+0100]):

Stephan Assmus wrote:
There is a description in UserBuildConfig.sample, don't know if it is what you need:
# Set the debug level for file src/bin/gdb/gdb/haiku-nat.c (note, that # the object file must be specified) to 1. It is worth mentioning, that the # executable the object file is linked into (gdb), will still be placed in # generated/objects/.../release/... Only when setting DEBUG for the # executable, too, it will be placed in .../debug_1/... DEBUG on <src!bin!gdb!gdb!>haiku-nat.o = 1 ;
I saw this, but this is per object file (and there are dozens of related object files). A way to selectively set debug mode for a specific library, binary or add-on is what I am looking for.
But the description text explicitely mentions being able to set DEBUG on the executable too. So I suppose this would work as well, have you tried and it doesn't? 
Didn't work. I added the following:

DEBUG on <src!servers!mail!>mail_daemon = 1 ;
DEBUG on <src!kits!mail!>libmail.so = 1 ;
DEBUG on <src!add-ons!mail_daemon!inbound_protocols!pop3!>POP3 = 1 ; DEBUG on <src!add-ons!mail_daemon!system_filters!inbox!>Inbox = 1 ; DEBUG on <src!add-ons!mail_daemon!system_filters!parser!>Message\ Parser = 1 ; 

Then I ran mail_daemon under Haiku with:

gdb /system/servers/mail_daemon

And GDb could not find any symbols.
Maybe the executables are placed in .../debug_1/... but the HaikuImage script still copies them from .../release/... ?
If you place the executables manually on the Haiku partition, does GDB find symbols then?
No files were generated inside the debug_1 hierarchy. In fact, this directory was not even created. 

-Bruno

Other related posts: