Description of problem: -set up in lazarus gdb debugger -run my program with breakpoint -crash Version-Release number of selected component: gdb-7.5.1-32.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/gdb -silent -i mi -nx crash_function: dump_core executable: /usr/bin/gdb kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 dump_core at ../../gdb/utils.c:694 #3 internal_vproblem at ../../gdb/utils.c:852 #5 internal_verror at ../../gdb/utils.c:877 #6 internal_error at ../../gdb/utils.c:887 #7 pop_subfile at ../../gdb/buildsym.c:711 #8 process_one_symbol at ../../gdb/dbxread.c:2987 #9 read_ofile_symtab at ../../gdb/dbxread.c:2644 #10 dbx_psymtab_to_symtab_1 at ../../gdb/dbxread.c:2441 #11 dbx_psymtab_to_symtab at ../../gdb/dbxread.c:2495 #13 psymtab_to_symtab at ../../gdb/psymtab.c:797 Potential duplicate: bug 716627
Created attachment 692036 [details] File: backtrace
Created attachment 692037 [details] File: cgroup
Created attachment 692038 [details] File: core_backtrace
Created attachment 692039 [details] File: dso_list
Created attachment 692040 [details] File: environ
Created attachment 692041 [details] File: limits
Created attachment 692042 [details] File: maps
Created attachment 692043 [details] File: open_fds
Created attachment 692044 [details] File: proc_pid_status
Created attachment 692045 [details] File: var_log_messages
The primary problem is that you had to use STABS format (fpc -gs). STABS is obsolete and unsupported. Use DWARF (fpc -g). I do not know how Lazarus passes this debug option to fpc. Could you attach the binary being debugged? Expecting it is: /home/karcsi/Program/lazarus/analizis/src/analizis
Created attachment 693552 [details] The binary This is the binary, what I ran in debug.
Lazarus debug settings: http://www.flickr.com/photos/90897110@N07/8447959777/in/photostream
Program settings, what I want to debug: http://www.flickr.com/photos/90897110@N07/8448026911/in/photostream Paste: http://www.szerencsejatek.hu/xls/otos.csv Then click on Letöltés. Consol output: TApplication.HandleException Unknown Run-Time error : 210 Stack trace: $00000000004FC88A MAGE7BOOLEAN;2A.;FREEDATA, line 111 of KENOANALIZIS__SETHUZASOK:F17 $00000000004FC7F6 line 104 of KENOANALIZIS__SETHUZASOK:F17 $000000000080EACA ? L M I $000000000066EE69 $00000033F4647A55 ** GLib:ERROR:gmain.c:2718:g_main_dispatch: assertion failed: (current->dispatching_sources == ¤t_source_link) Félbeszakítva (core készült)
Created attachment 693716 [details] Lazarus build options screenshot. The options for choosing debug format is elsewhere, see the attachment. But debugging in Lazarus apparently uses different options than those set there - during Build All there was no debug info in the executable (as is set by the default options in this screenshot). But during debugging there was debug info, and it was the correct DWARF. In your "analizis" executable I see a lot of STABS debug info: readelf -WS analizis: these two are STABS: [23] .stab PROGBITS 0000000000000000 69b950 048f38 [24] .stabstr STRTAB 0000000000000000 6e4888 192c7c these four are DWARF: [25] .debug_info PROGBITS 0000000000000000 877504 673a31 [26] .debug_abbrev PROGBITS 0000000000000000 eeaf35 010a12 [27] .debug_line PROGBITS 0000000000000000 efb947 0c1d67 [28] .debug_frame PROGBITS 0000000000000000 fbd6b0 0961f0 Maybe you link in some pre-built static libraries with STABS? When you run "maintenance info psymtabs" in GDB you get either these records, those are correct DWARF: { psymtab gtk2wsspin.pp ((struct partial_symtab *) 0x32b73c8) readin no fullname (null) text addresses 0x7ec420 -- 0x7ecab4 psymtabs_addrmap_supported yes globals (* (struct partial_symbol **) 0x2e41cd8 @ 2) statics (* (struct partial_symbol **) 0x378ce18 @ 154) dependencies (none) } Or these incorrect STABS records: { psymtab 5;2543;;FONTCHANGED::2549=##3;:14TCUSTOMCONTROL7TOBJECT;2A*114;2543;;SETCOLOR::2550=##3;:14TCUSTOMCONTROL14TGRAPHICSCOLOR;2A*122;2543;;PAINT::2551=##3;:14TCUSTOMCONTROL;2A*261;2543;;CREATE::2552=##2544;:__ct__14TCUSTOMCONTROL7POINTER10TCOMPONENT;2A*37;2543;;DESTROY::2553=##3;:__dt__14TCUSTOMCONTROL7POINTE---Type <return> to continue, or q <return> to quit--- R;2A*0;2543;;;~%4; ((struct partial_symtab *) 0x2e32448) readin no fullname (null) text addresses 0x837c6b -- 0x837c6b psymtabs_addrmap_supported no globals (none) statics (none) dependencies (none) } See there "psymtabs_addrmap_supported no". When you do: (gdb) info line *0x837c6b No line number information available for address 0x837c6b <DEBUGEND_OPENSSL> You may get a hint where functions like DEBUGEND_OPENSSL come from.
Created attachment 694696 [details] Lazarus 1.0.4 options This is my lazarus 1.0.4 linking settings.
You can close this bug report, because I had found the problem. It was lnet package. With lnet I was'nt able to debug my program, without this package everything went all right. Thank you for your help.
The lnet package is not distributed in Fedora I hope, at least I have not found it in Fedora. While it is a valid GDB bug with STABS I am not going to fix it myself, there are more serious GDB bugs to fix.