Re: Gdb Internal Error
Re: Gdb Internal Error
- Subject: Re: Gdb Internal Error
- From: Dong Feng <email@hidden>
- Date: Fri, 9 Jul 2010 10:05:22 +0800
I'm going to do what you say soon. On the other hand, I just tried
"atos" and it works with the dSYM well. So for now the dSYM is still
useful for me, something alleviate the gdb problem.
Thanks,
Dong
2010/7/9 Jim Ingham <email@hidden>:
> What you're doing seems correct from your description. This sounds like there's some problem with the debug info.
>
> Make a file called .gdbinit in your home directory, and put in it:
>
> set verbose on
>
> In the debugging pane of Xcode Preferences, there's a setting to generate the debugging log. Turn that on as well.
>
> Then run your debugging session to the point of failure. Then file a bug including the log file. We'll be able to tell from the log file which file gdb was reading when this error occurred, and then if you don't mind, get a dump of the dwarf from that file and have a look to see what is wrong.
>
> Thanks,
>
> Jim
>
>
> On Jul 8, 2010, at 4:26 AM, Dong Feng wrote:
>
>> I have a project which has several sub-projects. One of the
>> sub-projects is a static-library whose "debugging information format"
>> was set as "stabs." The project has two custom steps, among others, as
>> follows:
>> 1. Use "dsymutil -x" to extract all symbols to a dSYM file.
>> 2. Use "strip" to strip all symbols from the generated executable.
>>
>> Gdb could load the generated executable with dSYM successfully.
>>
>> After I changed the "debugging information format" of that sub-project
>> to DWARF, gdb reports the following error when load the executable
>> with dSYM:
>>
>> =============================
>> gdb stack crawl at point of internal error:
>> 0 gdb-i386-apple-darwin 0x00000001001076e7
>> internal_vproblem + 308
>> 1 gdb-i386-apple-darwin 0x00000001001078c1 internal_verror + 27
>> 2 gdb-i386-apple-darwin 0x000000010010795f align_down + 0
>> 3 gdb-i386-apple-darwin 0x00000001000b1fc4
>> find_partial_die_in_comp_unit + 79
>> 4 gdb-i386-apple-darwin 0x00000001000bd97f
>> find_partial_die + 626
>> 5 gdb-i386-apple-darwin 0x00000001000bd9cc
>> fixup_partial_die + 55
>> 6 gdb-i386-apple-darwin 0x00000001000be08d
>> scan_partial_symbols + 58
>> 7 gdb-i386-apple-darwin 0x00000001000be38e
>> scan_partial_symbols + 827
>> 8 gdb-i386-apple-darwin 0x00000001000bef51
>> dwarf2_build_psymtabs + 2982
>> 9 gdb-i386-apple-darwin 0x0000000100144af3
>> macho_symfile_read + 294
>> 10 gdb-i386-apple-darwin 0x000000010004bbb8
>> syms_from_objfile + 1401
>> 11 gdb-i386-apple-darwin 0x000000010004c601
>> symbol_file_add_with_addrs_or_offsets_using_objfile + 690
>> 12 gdb-i386-apple-darwin 0x000000010004c5bb
>> symbol_file_add_with_addrs_or_offsets_using_objfile + 620
>> 13 gdb-i386-apple-darwin 0x000000010004c894
>> symbol_file_add_name_with_addrs_or_offsets + 117
>> 14 gdb-i386-apple-darwin 0x000000010004cd5c
>> symbol_file_add_main_1 + 207
>> /SourceCache/gdb/gdb-1346/src/gdb/dwarf2read.c:8233: internal-error:
>> could not find partial DIE in cache
>>
>> A problem internal to GDB has been detected,
>> further debugging may prove unreliable.
>> ==============================
>>
>> If loading without dSYM, gdb do not complain.
>>
>> The project is quite complex and I may not be able to fully describe
>> it. But seems I didn't do anything having a chance to corrupt the
>> generated dSYM file. Is this a known problem, or did I miss any step
>> in generating the dSYM?
>>
>> Thanks,
>> Dong
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Xcode-users mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden