[maemo-developers] Segmentation fault in callback functions - maemo 4.0
From: Jakov dkymail at gmail.comDate: Mon Feb 18 18:16:47 EET 2008
- Previous message: Segmentation fault in callback functions - maemo 4.0
- Next message: Segmentation fault in callback functions - maemo 4.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yeah, it's the same to the N800 device. When I clicked on the button, the app exited at once. I used only ARMEL target for testing (simulation) and made .deb and installed on N800 device. On 2/18/08, Eero Tamminen <eero.tamminen at nokia.com> wrote: > Hi, > > ext Jakov wrote: > > I have a simple app with socket communication. In Maemo 3.x it worked > well. > > But the problem comes when I use Maemo 4.0 > > > > This line is ok when initializing: > > > > gtk_label_set_text (GTK_LABEL(communication_tab->label_connect), > "Connect"); > > > > > > The label has text "Connect"; > > > > When I click a button, I want to change its text, to "Reconnect", for > > example. A callback func is invoked, you know. But in this func, an error > > occurs: > > > > "qemu: uncaught target signal 11 (Segmentation fault) - exiting" > > > > It didn't happen in Maemo 3.x. > > > > Please tell me what's wrong. Thanks very much. > > Does it work on the target device? > > (ARM scratchbox target is really meant for building, use x86 target > if you want to do testing in addition to the device. On x86 you have > also tools like Valgrind for finding errors in your code better.) > > > - Eero >
- Previous message: Segmentation fault in callback functions - maemo 4.0
- Next message: Segmentation fault in callback functions - maemo 4.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]