форумы  помощь  поиск  регистрация  майллист  ВХОД  слежка

Вариант для распечатки		Архивированная нить - только для чтения!  Пред. тема | След. тема
Форумы Программирование под UNIX (Public)
Изначальное сообщение		[Проследить за развитием треда]

"using dlsym (FreeBSD 4.5)"
Сообщение от uin on 02-Апр-02, 18:50  (MSK)
Well so.c bool testFn(void) {    return true; } compiling... output shared object called test.so and then (wanna know symbols) bash> nm test.so 0000135c A _DYNAMIC 0000134c A _GLOBAL_OFFSET_TABLE_ 000013ac A __bss_start 000013ac A _edata 000013ac A _end 0000030c T testFn__Fv what is the suffix "__Fv" means... because of it the funstion dlsym returns NULL in response of bool (*fn)(); fn = (bool (*)()) dlsym("abs_path_to_test.so", "testFn"); Briefly: fn equals NULL because of no such symbol found in "test.so". Yes, there "testFn__Fv" instead of "testFn"... But why ? What is "__Fv" means & how can I prevent it's appearence... tnx
	Рекомендовать в FAQ | Cообщить модератору | Наверх

Индекс форумов | Темы | Пред. тема | След. тема

Сообщения по теме

1. "RE: using dlsym (FreeBSD 4.5)"
Сообщение от Soldier on 03-Апр-02, 07:03  (MSK)
>Well > >so.c > >bool testFn(void) >{ >   return true; >} > >compiling... output shared object called test.so > > >and then (wanna know symbols) bash> nm test.so > >0000135c A _DYNAMIC >0000134c A _GLOBAL_OFFSET_TABLE_ >000013ac A __bss_start >000013ac A _edata >000013ac A _end >0000030c T testFn__Fv > >what is the suffix "__Fv" means... >because of it the funstion >dlsym returns NULL in response >of > >bool (*fn)(); >fn = (bool (*)()) dlsym("abs_path_to_test.so", "testFn"); > > >Briefly: > >fn equals NULL because of no >such symbol found in "test.so". >Yes, there "testFn__Fv" instead of >"testFn"... But why ? What >is "__Fv" means & how >can I prevent it's appearence... > > >tnx This is because you are using C++ compiler and this language allows so called overriding. It means that you may define functions with same name but with diffirent types of parameters. To distinct such functions this suffix __?? is used. In your case testFn__Fv means testFn - far function with no arguments. If you define it like testFn(int) than you will see testFn_Fi symbol and so on. So use testFn_Fv instead of testFn or use C compiler instead of C++ one.
	Рекомендовать в FAQ | Cообщить модератору | Наверх

	2. "well"
	Сообщение от uin on 04-Апр-02, 12:52  (MSK)
	thank u, but how can I use classes ? (export/import. not objects but classes: class CTest for example. is it possible ?) tnx
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	3. "in details"
	Сообщение от uin on 04-Апр-02, 19:35  (MSK)
	Suppose, I have a multithreaded application (daemon) and a global pointer to some function described in 'so'. Why the following does not work (SIGSEGV've been sended) ? int (* fn)(); void foo() { //***   fn = (int (*)()) dlsym(handle_to_opened_so, "func name");   // returns ok //*** } void * thr_routine(void * _arg_p) {   //***     (*fn)(); // <- SIGSEGV   //***    return NULL; };
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	4. "RE: in details"
	Сообщение от Soldier on 05-Апр-02, 07:13  (MSK)
	>Suppose, I have a multithreaded application >(daemon) and a global pointer >to some function described in >'so'. Why the following does >not work (SIGSEGV've been sended) >? > >int (* fn)(); > >void foo() >{ >//*** > >  fn = (int (*)()) >dlsym(handle_to_opened_so, "func name"); >  // returns ok > >//*** >} > >void * thr_routine(void * _arg_p) >{ >  //*** >    (*fn)(); // ><- SIGSEGV >  //*** >   return NULL; >}; If realy everything OK it should work and  I have two suggestions why it not: 1. You are using dlopen after creating of thread (you MUST use it before). 2. Problem in implementation of 'func_name' As to previous question - sorry, but I do  not know how to use classes defined in dynamicaly loaded library directly (I used some ugly methods to do that), but why do not use this library as a shared? In this case there are no problems. Anyway, I will try to find out solution at weekends and if I succeed I will share results with you.
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	5. "no"
	Сообщение от uin on 05-Апр-02, 14:14  (MSK)
	sequence of actions: 1. obtaining the global (!) handle of 'so' (it's ok) 2. obtaining the global (!) poiter to some foo (it's ok) 3. for each thread (in thr_routine) call the 'some foo' talking above. 4. SIGSEGV the problem is that an appearece of kernel action number 4 terminates the programm (core dumped).
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	6. "RE: no"
	Сообщение от Soldier on 05-Апр-02, 15:04  (MSK)
	Ok. Lets clear situation. I suppose you are using libpthread. In this case, a sequence dlopen -> dlsym -> pthread_create should work properly and sequence: pthread_create -> dlopen -> dlsym or .... -> pthread_create -> dlsym should cause segmentation fault (SIGSEGV) Which sequence is used in you program? If you only want avoid an aborting of your program at receiving signal SIGSEGV, just catch this signal and  it is all.
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	7. "First"
	Сообщение от uin on 05-Апр-02, 16:18  (MSK)
	assuming that it's impossible to catch SIGSEGV. I do not wanna to explain such assumption (it's too long), but take it into account please.
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	8. "Done"
	Сообщение от uin on 05-Апр-02, 18:01  (MSK)
	I solved my problem. thank u.
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	10. "How to use C++ classes  via dynamic loaded library"
	Сообщение от Soldier on 07-Апр-02, 08:50  (MSK)
	If still actually: http://www.vidler.clara.net/dynamic.html I tested it and it works. Best
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	11. "thank u"
	Сообщение от uin on 08-Апр-02, 18:34  (MSK)
	COM like
		Рекомендовать в FAQ | Cообщить модератору | Наверх

	9. "RE: First"
	Сообщение от Soldier on 06-Апр-02, 21:10  (MSK)
	>assuming that it's impossible to catch >SIGSEGV In Linux ( I think in another *nix-es too) it possible. Of course you should teminate your program (using exit, for example) on catching this signal but you have possibility to settle some things down. >I do not wanna >to explain such assumption (it's >too long), but take it >into account please.
		Рекомендовать в FAQ | Cообщить модератору | Наверх

Удалить

Индекс форумов | Темы | Пред. тема | След. тема

Пожалуйста, прежде чем написать сообщение, ознакомьтесь с данными рекомендациями.