各位大大好:    小弟寫了一個so檔後... 想要另寫一個程式來使用它... 將so檔include進project後... build也過了... 但要執行時卻出現底下錯誤訊息... Project Project1 received signal SIGSEGV(11). Process stopped. Use Step or Run to continue. 請問要如何解決... 之前有寫過一個so檔可以使用... 這個so檔跟之前的那個有一個差別在於使用了 不知道是不是因為這個的緣故... 麻煩大家了...謝謝啦...

Make sure you do not use the VCL unit (e.g. Graphics, Forms, Printers, etc)

不好意思... 用到了HTML Tag... "這個so檔跟之前的那個有一個差別在於使用了 clx.h"

Yes... I have used TBitmap (because I have to read .bmp and .jpg) Is there any solution for me to use this component? Thanks a lot!

Oh... Kylix C ... for Kylix (Delphi), uses QGraphics if you misued Graphics... I think C should be similar, don't use Graphics, Forms, Printers and use QGraphics, QPrinters, QForms instead.

I have used QGraphics.hpp, but still have another problem. I have seen it in previous article, but it is not solved.    [Linker Fatal Error] Fatal: Unable to open file 'SysInit.o'    According to previous article, I have installed all development tools in my RedHat9, including Kernel development, X software development, GNOME, and KDE development. It's a strange problem, because I can run my source code but can't build .so file.

I have used QGraphics.hpp, but still have another problem. I have seen it in previous article, but it is not solved.    [Linker Fatal Error] Fatal: Unable to open file 'SysInit.o'    According to previous article, I have installed all development tools in my RedHat9, including Kernel development, X software development, GNOME, and KDE development. It's a strange problem, because I can run my source code but can't build .so file.

Sorry, I had made a mistake.  >

I am glad that you find the solution  >

I have tried to code a small program to load image by TBitmap in QGraphics.hpp, and the error signal still exists. Maybe Kylix still has bugs or I can't use QGraphics in this way, so I give up to use this component. Now, I have to read BMP and JPG by some open source codes or by myself. Thank you for your help, Mr. william!  >

I have tried to create a simple application on both Kylix Delphi and C++ and have no problem in loading a bitmap using TBitmap  href="http://mitglied.lycos.de/AndreasHausladen/Delphi/Kylix/CLXPatches/">http://mitglied.lycos.de/AndreasHausladen/Delphi/Kylix/CLXPatches/ P.S. I have not applied the patch since my use of Kylix on Linux is for fun only

I can also load image by TBitmap, but it will signal an error when I use it in .so file. I build a Share Object project, and select Cpp source type and "use CLX". Write source codes below, and add test.cpp file to project. 1."test.h" extern "C" __declspec(dllexport) void LoadImage(char *filename, unsigned char **outmap); 2."test.cpp" #include "test.h" #include "QGraphics.hpp" const int level = 4; extern "C" __declspec(dllexport) void LoadImage(char* filename, unsigned char **outmap) { TBitmap *image = new TBitmap(); image->LoadFromFile( filename ); outmap = new unsigned char* [image->Height]; for (int i=0; i< image->Height; i ) outmap[i] = new unsigned char [image->Width]; Byte *ptr; for (int i=0; i< image->Height; i ) { ptr = (Byte *)image->ScanLine[i]; for (int j=0; j< image->Width; j ) outmap[i][j] = ptr[level*j]; } delete image; } Select Project->Options... in main menu, and click Packages. Unselect "Build with runtime package". After build this project, add .so file to your test program (add .so file to project, and include "test.h"). When you call LoadImage() in your program and run it, the error signal will show. I have updated VisualCLX you mentioned above, but the error is still happened. ps. My code is just for test, so I don't free the outmap memory and don't check if the filename is an image format. 發表人 - chrono 於 2003/11/28 15:05:44

Found this is QForms.pas (not QForms.hpp) line 721:

引言: { Restrictions on CLX and TApplication in external modules: CLX and Qt allow only a single instance of the application object - it is created and destroyed in the initialization and finalization sections of QControls.pas, respectively. It is the user's responsibility when using external modules (packages and libraries or shared objects) in their applications to ensure that only a single instance of TApplication is created. Please heed the following rules when mixing modules that rely on visual CLX: - External libraries (.dll's/.so's) may not refer to visual CLX units directly or indirectly. - If you wish to include visual CLX code in an external library, the external library must be a *package* to avoid duplicate unit initialization and finalization. - If your package uses the visualclx package, the main application must also use it, and should not directly link in visual CLX units. }

Then it explains why... Build with runtime package is required. Personally I don't have Kylix C experience on using package. I do have a project based on packages/shared objects running sucessfully using Kylix Delphi.

I have solved this problem by an image library(FreeImage) to load image instead of TBitmap. It's usage is not convenient.  I cannot use it to read image data in main program immediately, but I have to use it in another .cpp or .so file. Maybe I should address this question on their forum. 

.so can create clx component, I actually has .so creating database component in one of my personal project. The only limitation is you should run the same instance of CLX in both the application and the .so file (i.e. runtime package only).    VCL suffers from this too  >>