Re: 【数亿娱乐】稳如泰山【708227】 【主管 直属 招商 总代 开户】 数亿娱乐隆重登场 新濠集团旗下 实力雄厚 信誉优秀 您不能错过 快速注册http://ez2o.com/4gJjE

[蕾宝708227]

蕾宝708227於 2017年11月1日星期三 UTC+8下午12時33分26秒寫道：
> 【数亿娱乐】稳如泰山【708227】
> 【主管 直属 招商 总代 开户】
> 数亿娱乐隆重登场  新濠集团旗下 
> 实力雄厚 信誉优秀  您不能错过
> 快速注册http://ez2o.com/4gJjE

【玖富娱乐】推荐主管QQ【708227】
【玖富娱乐】推荐主管QQ【708227】
【玖富娱乐】推荐主管QQ【708227】
【玖富娱乐】推荐主管QQ【708227】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[蕾宝708227]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【玖富娛樂】實力招商QQ【708227】
【玖富娛樂】實力招商QQ【708227】
【玖富娛樂】實力招商QQ【708227】
【玖富娛樂】實力招商QQ【708227】
【玖富娛樂】實力招商QQ【708227】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【数亿娱乐】稳如泰山【708227】 【主管 直属 招商 总代 开户】 数亿娱乐隆重登场 新濠集团旗下 实力雄厚 信誉优秀 您不能错过 快速注册http://ez2o.com/4gJjE

[数亿开户]

【数亿娱乐】稳如泰山【708227】
【主管 直属 招商 总代 开户】
数亿娱乐隆重登场  新濠集团旗下 
实力雄厚 信誉优秀  您不能错过
快速注册http://ez2o.com/4gJjE


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[数亿开户]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【数亿娱乐】稳如泰山【708227】
【主管 直属 招商 总代 开户】
数亿娱乐隆重登场  新濠集团旗下 
实力雄厚 信誉优秀  您不能错过
快速注册http://ez2o.com/4gJjE


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[winwinwin6996]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc
【数亿娱乐】稳如泰山【708227】
【主管 直属 招商 总代 开户】
数亿娱乐隆重登场  新濠集团旗下 
实力雄厚 信誉优秀  您不能错过
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[数亿开户]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【数亿娱乐】【Q1192431153】
 “寻人!!!寻志同道合之人、寻竭忠尽智之人、寻深思远虑之人、寻勤恳至诚之人”
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【数亿娱乐】【Q1192431153】 “寻人!!!寻志同道合之人、寻竭忠尽智之人、寻深思远虑之人、寻勤恳至诚之人”

[数亿开户]

【数亿娱乐】【Q1192431153】
 “寻人!!!寻志同道合之人、寻竭忠尽智之人、寻深思远虑之人、寻勤恳至诚之人”
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[winwinwin6996]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【数亿娱乐】【Q1192431153】【主管 直属 招商 总代 开户】【加我备注88】
数亿娱乐隆重登场  新濠集团旗下 
实力雄厚 信誉优秀  您不能错过
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 【数亿娱乐】【Q1192431153】【主管 直属 招商 总代 开户】【加我备注88】

[winwinwin6996]

壹壹玖於 2017年9月3日星期日 UTC+8下午4時18分05秒寫道：
> 数亿娱乐隆重登场  新濠集团旗下 实力雄厚信誉优秀 您不能错过
> 【数亿娱乐】【Q1192431153】【主管 直属 招商 总代 开户】【加我备注88】

【数亿娱乐】【Q1192431153】【主管 直属 招商 总代 开户】【加我备注88】
数亿娱乐隆重登场  新濠集团旗下 
实力雄厚 信誉优秀  您不能错过
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

数亿娱乐隆重登场 新濠集团旗下 实力雄厚信誉优秀 您不能错过 【数亿娱乐】【Q1192431153】【主管 直属 招商 总代 开户】【加我备注88】

[壹壹玖]

数亿娱乐隆重登场  新濠集团旗下 实力雄厚信誉优秀 您不能错过
【数亿娱乐】【Q1192431153】【主管 直属 招商 总代 开户】【加我备注88】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【数亿娱乐】【Q1192431153】【主管 直属 招商 总代 开户】【加我备注88】

[壹壹玖]

数亿娱乐隆重登场  新濠集团旗下 实力雄厚信誉优秀 您不能错过
【数亿娱乐】【Q1192431153】【主管 直属 招商 总代 开户】【加我备注88】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[壹壹玖]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【数亿娱乐】【Q1192431153】【直属 主管 招商 总代 开户】【加我备注88】
【数亿娱乐】【Q1192431153】【直属 主管 招商 总代 开户】【加我备注88】


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【数亿娱乐】【Q1192431153】【直属 主管 招商 总代 开户】【加我备注88】 【数亿娱乐】【Q1192431153】【直属 主管 招商 总代 开户】【加我备注88】

[壹壹玖]

【数亿娱乐】【Q1192431153】【直属 主管 招商 总代 开户】【加我备注88】
【数亿娱乐】【Q1192431153】【直属 主管 招商 总代 开户】【加我备注88】


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[壹壹玖]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】
数亿娱乐隆重登场  新濠集团旗下 实力雄厚信誉优秀 您不能错过

【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】
数亿娱乐隆重登场  新濠集团旗下 实力雄厚信誉优秀 您不能错过
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】 数亿娱乐隆重登场 新濠集团旗下 实力雄厚信誉优秀 您不能错过

[壹壹玖]

【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】
数亿娱乐隆重登场  新濠集团旗下 实力雄厚信誉优秀 您不能错过

【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】
数亿娱乐隆重登场  新濠集团旗下 实力雄厚信誉优秀 您不能错过
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】

[壹壹玖]

壹壹玖於 2017年8月19日星期六 UTC+8下午5時48分30秒寫道：
> 【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】

【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】
数亿娱乐隆重登场  新濠集团旗下 实力雄厚信誉优秀 您不能错过
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】

[壹壹玖]

【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[壹壹玖]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【数亿娱乐】【Q1192431153】【直属主管招商总代开户】【加我备注88】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】

[壹壹玖]

【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[壹壹玖]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】

[winwinwin6996]

【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
【数亿娱乐】【Q1192431153】【加我备注88】【直属 主管 招商 总代 开户】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[壹壹玖]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【数亿娱乐】【直属 主管 招商 总代 开户】【Q1192431153】【加我备注88】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【数亿娱乐】【直属 主管 招商 总代 开户】【Q1192431153】【加我备注88】

[壹壹玖]

【数亿娱乐】【直属 主管 招商 总代 开户】【Q1192431153】【加我备注88】
【数亿娱乐】【直属 主管 招商 总代 开户】【Q1192431153】【加我备注88】
【数亿娱乐】【直属 主管 招商 总代 开户】【Q1192431153】【加我备注88】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

数亿娱乐隆重登场 新濠集团旗下 实力雄厚信誉优秀 您不能错过

[壹壹玖]

【数亿娱乐】【直属 主管 招商 总代 开户】【Q1192431153】【加我备注88】
【数亿娱乐】【直属 主管 招商 总代 开户】【Q1192431153】【加我备注88】
【数亿娱乐】【直属 主管 招商 总代 开户】【Q1192431153】【加我备注88】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

数亿娱乐隆重登场 新濠集团旗下 实力雄厚信誉优秀 【数亿娱乐】【直属、主管、招商、总代、开户】【企鹅1192431153】【加我备注88】

[壹貳酸]

数亿娱乐隆重登场  新濠集团旗下 实力雄厚信誉优秀 您不能错过
【数亿娱乐】【直属、主管、招商、总代、开户】【企鹅1192431153】【加我备注88】
【数亿娱乐】【直属、主管、招商、总代、开户】【企鹅1192431153】【加我备注88】
数亿娱乐主管Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐主管Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐直属Q：1192431153
　　数亿娱乐挂机软件
　　数亿娱乐主管
　　数亿娱乐招商
　　数亿娱乐直属
　　数亿娱乐总代
　　数亿娱乐开户
　　数亿娱乐主管
　　数亿娱乐招商
　　数亿娱乐直属
　　数亿娱乐总代
　　数亿娱乐开户
　　数亿娱乐主管
　　数亿娱乐招商
　　数亿娱乐直属
　　数亿娱乐总代
　　数亿娱乐开户
　　数亿娱乐主管
　　数亿娱乐招商
　　数亿娱乐直属
　　数亿娱乐总代
　　数亿娱乐开户
　　数亿娱乐直属Q：1192431153
　　数亿娱乐挂机软件
　　数亿娱乐主管
　　数亿娱乐招商
　　数亿娱乐直属
　　数亿娱乐总代
　　数亿娱乐开户
　　数亿娱乐主管
　　数亿娱乐招商
　　数亿娱乐直属
　　数亿娱乐总代
　　数亿娱乐开户
　　数亿娱乐主管
　　数亿娱乐招商
　　数亿娱乐直属
　　数亿娱乐总代
　　数亿娱乐开户
　　数亿娱乐主管
　　数亿娱乐招商
　　数亿娱乐直属
　　数亿娱乐总代
　　数亿娱乐开户
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

【sky、数亿娱乐直属】【Q1192 4311 53】【加我备注88】 【sky、数亿娱乐直属】【Q1192 4311 53】【加我备注88】

[壹貳酸]

【sky、数亿娱乐直属】【Q1192 4311 53】【加我备注88】
【sky、数亿娱乐直属】【Q1192 4311 53】【加我备注88】
捷豹系统皇冠旗下 SKY娱乐是台湾捷豹HG旗下平台，实力雄厚信誉优秀！
SKY娱乐。玩法齐全、真人视讯！
快速注册 https://ez2o.com/9855h
SKY视频https://v.qq.com/x/page/z0382b8vgf3.html
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: 彩票500万

[b54132001]

彩票500万於 2002年8月18日星期日 UTC+8下午12時00分39秒寫道：
> 这里有对足球彩票、全国各地体彩、风采和六合彩的精确预测及预测电子杂志、彩票预测软件、彩票预测书刊、预测技术方法、以及最快的赚钱方式。
> 《彩票王》软件预测全国各地多种体育彩票、福利彩票、足球彩票、四花选四、天天彩、五字彩、奥运彩票、香港六合彩、台湾乐透彩等。《彩票王》是目前全国功能最强大、种类最全面的彩票选号分析决策软件系统。
>更详细情况请到这里查看：http://www.tjw.cc

【sky娱乐直属】【Q1192431153】【加我备注88】
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Wrong backtrace debugging armcc generated elf

[menion]

Hi all
I'm wondering if anyone can help on this subject.
I have reached a decent success in debugging a monolithic application running 
on a Cortex R4 with an embedded kernel, using Segger JLink debugger gdbserver 
and a windows gdb for ARM target, taken from the GNU ARM Embedded project. 
Everything under the umbrella and the help of GNU ARM Eclipse plugin.
This is the info from the gdb I use:

GNU gdb (GNU Tools for ARM Embedded Processors) 7.10.1.20160210-cvs
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".

The application is compiled with armcc 5.0.1 (no room for changing it).
The info I can get from file on the elf target:

A2TK_PRJ.out: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically 
linked, not stripped

As I have said everything works quite ok, I can control the target, break, walk 
through the code. What it is not working is the backtrace. What I see is that 
GDB gets a kind of confused, it seems it cannot understand correctly the 
current frame info and tries to access to some wrong memory location.
Is it anything I can fix with some settings or it is a known limitation when 
debugging armcc generated elf?
Thanks
Bye
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

how can i modify a vertor when debug a C++ code with GDB.

[qianyingshuo0099]

Hi all
   i am a fresh man of using GDB, now i want to modify a vertor container in 
GDB.

>>> code

if(cTestVec.empty())
{
return -1
}

>>> end

well, The param cTestVec is empty. but i want modify is when degueing.

thk u everyone!
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Working on breakpoint.c

[Aashish R]

I wanted a feature in breakpoint.c file about a statement like if user
gives break * it will show list of functions available to apply break in
given program.How would i go about coding this feature?

Regards,
Aashish R
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

request to change from curses to ncurses

[jmichae3]

just for my own sanity...
I have had enough problems with curses in my life, don't need more...
I do need a debugger though, desperately.
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

wh command without argument to gdb in Emacs shell buffer == utter confusion

[ishikawa]

wh command without argument to gdb in Emacs shell buffer

Running gdb in Emacs's shell-mode buffer and then issueing wh
without argument by mistake causes GDB to get hung (without no visible
activity) [or rathr print long blank lines without prompt!?]

I am perplexed as to what is going on as I uncover a few things along
the way.

Below, a  log is excerpted.

---

Note 1: I am NOT using Emacs's gdb-mode when this happens.  I type
gdb as an ordinary shell command within the Emacs's shell buffer.

Note 2: Background.

In the old days, wh would be considered a shorthand for where
command.  But today there is winheight command and wh is regarded
as a shorthand for it.  An old timer like me types wh as a shorthand
for where without argument, and noticed this strange problem.

After a few days of pondering and trying to fix various issues like
missing shared library symbols, etc., finally I got curious and typed
help wh and found out about this winheight command. So I was
typing winheight command instead of where all along.

Note 3: If I use gdb in an ordinary terminal screen, say, without
argument and type wh to gdb prompt,

$ gdb
gdb wh

I get a small popup window, and in this case, it says, No source
available
and the usage help is printed to the original tty console where gdb
prompt appears, and prompt returns.
[I mistook this popup window as a X window, but no, it seems
it is a text rectangle created by termcap library or similar! This is
a source of confusion on my analysis. This confusion is in this writeup.]

That is good.

In emacs's shell-buffer usage, there is no indication of either (no
window, no help message to the prompt. Well, control-C does not seem
to work, but please read the excerpt log #2 at the end.)

To wit, here is the log from within Emacs's shell buffer.
The first run of gdb simply prints the help message for wh and quits.
The second run gets hung after I type wh.

[Ugh! No, as I write this message, I got still wiser and hit C-MC-J to
this seemingly hung gdb and I got gdb prompt again.  What is going
on? More in the Log #2 at the end.]


Log 1:
--- begin quote ---
ishikawa@debian-vbox-ci:/home/ishikawa$ gdb
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i486-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) help wh
Set the height of a specified window.
Usage: winheight win_name [+ | -] #lines
Window names are:
src  : the source window
cmd  : the command window
asm  : the disassembly window
regs : the register display

(gdb) quit
ishikawa@debian-vbox-ci:/home/ishikawa$ gdb
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i486-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) wh




   



---

As you can see, control-C won't interrupt gdb.
I have to kill gdb from another console.
[But please read the log #2 excerpt at the end. It seems that there is
another process running in a mixed manner in this terminal.]

This is a major usability issue.

Merely typing a command without an argument should not
render gdb unusable.

Yes, I think emacs might be setting up a strange environment for
gdb, but gdb code should be ready for failing to open a X window,
etc.

TIA

My Environment:
gdb --version
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i486-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
ishikawa@debian-vbox-ci:/home/ishikawa$ emacs --version
GNU Emacs 24.4.1
Copyright (C) 2014 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
ishikawa@debian-vbox-ci:/home/ishikawa$ uname -a
Linux debian-vbox-ci 3.2.0-4-686-pae #1 SMP Debian 3.2.57-3+deb7u2 i686
GNU/Linux

OS Issue:
The particular log was obtained 

Re: wh command without argument to gdb in Emacs shell buffer == utter confusion

[Pedro Alves]

On 10/29/2014 05:10 AM, ishikawa wrote:
 $ env | grep TERM
 TERM=dumb
 TERMCAP=

Right, we can reproduce this on the terminal with just:

 $ TERM=dumb gdb -q -nx
 (gdb) wh

I'm working on a fix that will make GDB error out instead
of hanging, like:

 $ TERM=dumb gdb -q -nx
 (gdb) wh
 Cannot enable the TUI: terminal doesn't support cursor addressing.
 (gdb)

Thanks,
Pedro Alves


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

The call stack can't include the right symbol for a weak symbol in dynamic library

[xiaofeng.yan]

Hi all,

I debug program with gdb on arm platform. The environment is as follow:

platform: vexpress(virtual app:ds:virtual machine app:ds:machine for 
arm on qemu)

libc: uclibc

A error information happen when debug the next codes.
0xb6fa0440 in ?? () from /lib/libc.so.0

The call stack can't include the right symbol of function pause(); I 
found that the function pause() is a weak symbol in dynamic library libc.
I don't know the reason  why gdb can't get the right symbol from the 
call stack?  Is this error from gdb or uclibc.
Is there any suggestion about this error?  I will be very grateful for 
your any reply.




code:
 relativedebug.c :
 #include unistd.h
#include stdlib.h
#include signal.h


static void handler (int signo)
{
abort ();
}

int main (void)
{
signal (SIGALRM, handler);
alarm (1);
pause ();
pause ();
return 0;
}

-bash-4.2# '/usr/bin/'gdb relativedebug
delete breakpoints
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
http://gnu.org/licenses/gpl.html http://gnu.org/licenses/gpl.html%3E%5EM

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as arm-euler-linux-gnueabi.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/... 
http://www.gnu.org/software/gdb/bugs/%3E...%5EM

Reading symbols from /tmp/for_gdb_test/base_test/relativedebug...done.
(gdb) delete breakpoints
(gdb) break main
Breakpoint 1 at 0x8548: file relativedebug.c, line 30.
(gdb) run
Starting program: /tmp/for_gdb_test/base_test/relativedebug

Breakpoint 1, main () at relativedebug.c:30
30  signal (SIGALRM, handler);
(gdb) continue
Continuing.

Program received signal SIGABRT, Aborted.
0xb6fdb7f0 in raise () from /lib/libc.so.0
(gdb) bt
#0  0xb6fdb7f0 in raise () from /lib/libc.so.0
#1  0xb6fd5bf4 in abort () from /lib/libc.so.0^M
#2  0x8540 in handler (signo=14) at relativedebug.c:25^M
#3  signal handler called^M
#4 0xb6fa0440 in ?? () from /lib/libc.so.0
#5  0x8564 in main () at relativedebug.c:32
(gdb)

Thanks
Yan



___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: wh command without argument to gdb in Emacs shell buffer == utter confusion

[ISHIKAWA,chiaki]

Dear Pedro Alves,

 On 10/29/2014 05:10 AM, ishikawa wrote:
 $ env | grep TERM
 TERM=dumb
 TERMCAP=
 
 Right, we can reproduce this on the terminal with just:
 
  $ TERM=dumb gdb -q -nx
  (gdb) wh
 
 I'm working on a fix that will make GDB error out instead
 of hanging, like:
 
  $ TERM=dumb gdb -q -nx
  (gdb) wh
  Cannot enable the TUI: terminal doesn't support cursor addressing.
  (gdb)
 
 Thanks,
 Pedro Alves

Thank you very much for your debugging effort.

After learning about TUI, I thought disabling this feature
based on the terminal capability would be one way to handle this issue.
So your patch would be very much appreciated.

Still being puzzled why I didn't realize this TUI feature for such a
long time. It is not clear when TUI is enabled in Debian Package.
It is possible it was not enabled even in the current release and only
enabled in Jessie (experimental and the would be mainline release in the
next release cycle).

Thank you again.

Best Regards,
Chiaki Ishikawa




___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: wh command without argument to gdb in Emacs shell buffer == utter confusion

[Pedro Alves]

On 10/29/2014 02:41 PM, ISHIKAWA,chiaki wrote:

 Thank you very much for your debugging effort.

No problem.  I use the TUI myself every day.

FYI, the bug is fixed on mainline now:

  https://sourceware.org/ml/gdb-patches/2014-10/msg00798.html

 Still being puzzled why I didn't realize this TUI feature for such a
 long time. It is not clear when TUI is enabled in Debian Package.
 It is possible it was not enabled even in the current release and only
 enabled in Jessie (experimental and the would be mainline release in the
 next release cycle).

No idea here.  The TUI has been in GDB for ages.

Thanks,
Pedro Alves


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Broken link on www.gnu.org

[Sergio Durigan Junior]

On Monday, October 13 2014, Василий Ёркин wrote:

 It seems that link to russian gdb user man is broken for some reason:
 http://www.gnu.org/software/gdb/documentation/

Hello Vasiliy,

Thanks for pointing that out.  I fixed this by removing the reference to
the link.

By the way, this list is not being used by the community anymore, and
only a few of us (GDB developers) keep an eye here.  For future
questions or comments, please use g...@sourceware.org or file a bug in
our bugzilla: http://sourceware.org/bugzilla.

Thanks,

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: gdb cannot find line numbers of certain weak symbols during backtrace

[Sergio Durigan Junior]

On Monday, October 13 2014, Runip Gopisetty wrote:

 Category
 GDB.

 Synopsis
 gdb cannot find line numbers of certain weak symbols during backtrace

Hello Runip,

Could you please file this bug on http://sourceware.org/bugzilla?
This list is not being used by GDB developers anymore.

Thanks,

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

gdb cannot find line numbers of certain weak symbols during backtrace

[Runip Gopisetty]

Category
GDB.

Synopsis
gdb cannot find line numbers of certain weak symbols during backtrace

Confidential
No

Severity
Serious

Priority
Medium

Submitter-Id
net.

Release
% gdb
GNU gdb (GDB) 7.7

Environment
* the operating system verson (output of uname -a)
Linux lc-sj1-4507 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 
x86_64 x86_64 x86_64 GNU/Linux
* the compiler version (for GCC, the output from gcc -v)
g++ (GCC) 4.7.2
* how GDB was configured (the This GDB was configured as line from 
GDB's startup text)
This GDB was configured as x86_64-unknown-linux-gnu.
How-To-Repeat

  Unfortunately I don't have a simple testcase to repeat. I will work 
on it in the background, to see if I can reproduce it.

Here are the compile flags I used:

g++ -O0 -ggdb -pthread -m32  -fPIC -Wall -Wno-unknown-pragmas -Wno-error 
-Wno-deprecated  -Wno-unused-variable -Wno-overloaded-virtual -Wno-enum-compare 
-Wno-write-strings -fpermissive -Wno-div-by-zero ...

I have also tried -fno-inline and it made no difference.

Description

The problem is that gdb does not print line numbers for only couple items in 
the stack frame even though everything was built using the -ggdb switch. Here 
is a stack trace, notice that #10 and #11 do not have the file and line numbers 
associated with them, everything else does.

(gdb) where
#0  0xe410 in __kernel_vsyscall ()
#1  0x002d5df0 in raise () from /lib/libc.so.6
#2  0x002d7701 in abort () from /lib/libc.so.6
#3  0x002cf26b in __assert_fail () from /lib/libc.so.6
#4  0x082e0d0f in 
FLEX_HASH_TABLE::search_bankTD3::uft_search_stage_params::check_base_entry_width
 (this=0x8a88f7c BM_BaseTest::Iss+65564,
base_entry_width=4, req_in=...)
at 
/projects/ntsw-arch3/AV/users/runipg/rg_arch2/arch/include/ip/flex_hash_table/src/search_bank.h:1119
#5  0x082dd698 in 
FLEX_HASH_TABLE::search_bankTD3::uft_search_stage_params::table_search 
(this=0x8a88f7c BM_BaseTest::Iss+65564, req_in=...,
rst_out=...)
at 
/projects/ntsw-arch3/AV/users/runipg/rg_arch2/arch/include/ip/flex_hash_table/src/search_bank.h:717
#6  0x082da27d in 
FLEX_HASH_TABLE::search_bankTD3::uft_search_stage_params::process_bank_req 
(this=0x8a88f7c BM_BaseTest::Iss+65564, req_in=...,
rst_out=...)
at 
/projects/ntsw-arch3/AV/users/runipg/rg_arch2/arch/include/ip/flex_hash_table/src/search_bank.h:324
#7  0x082d952d in 
FLEX_HASH_TABLE::search_stageTD3::uft_search_stage_params::process_req 
(this=0x8a78f60 BM_BaseTest::Iss, req=..., rst=...)
at 
/projects/ntsw-arch3/AV/users/runipg/rg_arch2/arch/include/ip/flex_hash_table/src/search_stage.h:307
#8  0x0833f085 in TD3::fb_uft_ss::process_req (
this=0x8a78f60 BM_BaseTest::Iss, req=..., rst=...)
at 
/projects/ntsw-arch3/AV/users/runipg/rg_arch2/arch/ip/flex_hash_table/src/trident3/fb_uft_ss.cc:32
#9  0x082e34b7 in FLEX_HASH_TABLE::search_stages::process_search_req (
this=0x8c16918, req=..., rst=...)
at 
/projects/ntsw-arch3/AV/users/runipg/rg_arch2/arch/include/ip/flex_hash_table/src/search_stages.h:176
#10 0x0833554c in 
FLEX_HASH_TABLE::flex_hash_tableTD3::fb_l3_search::l3_ht_params::process_table_req(FLEX_HASH_TABLE::REQ_BUS,
 FLEX_HASH_TABLE::RST_BUS) ()
#11 0x08332de3 in 
FLEX_HASH_TABLE::flex_hash_tableTD3::fb_l3_search::l3_ht_params::hash_table_lookup(SchanMsg,
 FLEX_HASH_TABLE::flex_hash_table_width_t) ()
#12 0x0833127f in TD3::fb_l3_search::table_lookup (
this=0x8ab9000 BM_BaseTest::l3_search, smsg=..., table_type=3284)
at 
/projects/ntsw-arch3/AV/users/runipg/rg_arch2/arch/ip/flex_hash_table/src/trident3/fb_l3_search.cc:310

I looked through the object files using nm and the executable using 
readelf. These symbols are listed as weak symbols.

% readelf -t --wide --symbols test_flex_ht.linux | grep l3_search | grep 
hash_table_lookup
43328: 08332ca8   810 FUNCWEAK   DEFAULT   12 
_ZN15FLEX_HASH_TABLE15flex_hash_tableIN3TD312fb_l3_search12l3_ht_paramsEE17hash_table_lookupER8SchanMsgNS_23flex_hash_table_width_tE
Just FYI, the object itself lives in a static global store.


Thanks for looking into it!


Runip

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Displaying structure members named like C keywords.

[Emilio Lopes]

2014-08-26 21:30 GMT+02:00 Sergio Durigan Junior sergi...@sergiodj.net:
 Aha, yeah, I was indeed suspecting that libstdc++'s debuginfo would be
 the cause.  I managed to reproduce it here. [...]

Hello Sergio,

that's indeed good news, thank you very much for your efforts!

 Meanwhile, I strongly advise you to file a bug against GDB on
 https://sourceware.org/bugzilla.  Also, please be aware that this
 list (bug-gdb@gnu.org) is not used by most of GDB developers
 anymore; there's just a few of us hanging around here.  Instead,
 the official mailing list for users is g...@sourceware.org.

Yes, I'm aware of this.  Nevertheless the fact that I need to create
yet another account kept me from using the bugzilla interface.
It seems to me like an unnecessary barrier for an occasional bug reporter.

All the best!

 Emílio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Displaying structure members named like C keywords.

[Sergio Durigan Junior]

On Wednesday, August 27 2014, Emilio Lopes wrote:

 Yes, I'm aware of this.  Nevertheless the fact that I need to create
 yet another account kept me from using the bugzilla interface.
 It seems to me like an unnecessary barrier for an occasional bug reporter.

Yeah, I understand and agree with you :-).  If you wish, I can create
the bug for you, and put you on the Cc list.  How does that sound?

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Displaying structure members named like C keywords.

[Emilio Lopes]

2014-08-27 15:45 GMT+02:00 Sergio Durigan Junior sergi...@sergiodj.net:
 Yeah, I understand and agree with you :-).  If you wish, I can create
 the bug for you, and put you on the Cc list.  How does that sound?

That's very nice from you, thank you very much!

 Emílio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Displaying structure members named like C keywords.

[Emilio Lopes]

Hello Sergio,

I was able to reproduce this issue on the host (x86_64 GNU/Linux)!

Here we go:

$ cat gdb-reproducer.c
#include iostream

using std::cout;

typedef struct {
int rlevel;
int complex;
} param_t;

int main(int argc, char *argv[]) {
param_t foo;

foo.rlevel = 4;
foo.complex= foo.rlevel + 11;

cout  foo.complex:   foo.complex  \n;

return(0);
}

$ g++ -Wall -ggdb3  gdb-reproducer.c  ./a.out
foo.complex: 15

$ gdb a.out
GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from a.out...done.
(gdb) b main
Breakpoint 1 at 0x4007c6: file gdb-reproducer.c, line 13.
(gdb) r
Starting program: /home/lopes/projects/c/a.out

Breakpoint 1, main (argc=1, argv=0x7fffe958) at gdb-reproducer.c:13
13foo.rlevel = 4;
(gdb) n
14foo.complex= foo.rlevel + 11;
(gdb) n
16cout  foo.complex:   foo.complex  \n;
(gdb) p foo
$1 = {rlevel = 4, complex = 15}
(gdb) ptype foo
type = struct param_t {
int rlevel;
int complex;
}
(gdb) p foo.complex
A syntax error in expression, near `'.
(gdb) info shared
FromTo  Syms Read   Shared Object Library
0x77ddcae0  0x77df5170  Yes
/lib64/ld-linux-x86-64.so.2
No  linux-vdso.so.1
0x77b2c8e0  0x77b9480a  Yes
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
0x777d5580  0x77840de6  Yes
/lib/x86_64-linux-gnu/libm.so.6
0x775bcab0  0x775cc995  Yes
/lib/x86_64-linux-gnu/libgcc_s.so.1
0x772304a0  0x7735a613  Yes
/lib/x86_64-linux-gnu/libc.so.6
(gdb) noshared
(gdb) p foo.complex
$2 = 15
(gdb) p foo
$3 = {rlevel = 4, complex = 15}
(gdb) p foo.complex
$4 = 15
(gdb) shared libstdc.*
Reading symbols from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6...Reading symbols from
/usr/lib/debug//usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.20...done.
done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) p foo.complex
A syntax error in expression, near `'.
(gdb) p foo
$5 = {rlevel = 4, complex = 15}
(gdb) ptype foo
type = struct param_t {
int rlevel;
int complex;
}

It seems that something in the debug info of libstdc++ is causing the problem.

Some info about the system I'm using:

$ uname -a
Linux lopes 3.14-1-amd64 #1 SMP Debian 3.14.12-1 (2014-07-11)
x86_64 GNU/Linux
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian
4.9.1-4' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.9 --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
--enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre
--enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64
--with-arch-directory=amd64
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc
--enable-multiarch --with-arch-32=i586 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.1 (Debian 4.9.1-4)
$ dpkg -l | grep -F 'libstdc++'
ii  libstdc++-4.9-dev:amd64 4.9.1-4  amd64GNU
Standard C++ Library v3 (development files)
ii  libstdc++6:amd644.9.1-4  amd64GNU
Standard C++ Library v3
  

Re: Displaying structure members named like C keywords.

[Sergio Durigan Junior]

On Tuesday, August 26 2014, Emilio Lopes wrote:

 Hello Sergio,

 I was able to reproduce this issue on the host (x86_64 GNU/Linux)!


[...]

 It seems that something in the debug info of libstdc++ is causing the problem.

Aha, yeah, I was indeed suspecting that libstdc++'s debuginfo would be
the cause.  I managed to reproduce it here.  I still need to investigate
this in order to identify what's going on, and I think I'll be able to
do this only on the weekend.  Meanwhile, I strongly advise you to file a
bug against GDB on https://sourceware.org/bugzilla.  Also, please be
aware that this list (bug-gdb@gnu.org) is not used by most of GDB
developers anymore; there's just a few of us hanging around here.
Instead, the official mailing list for users is g...@sourceware.org.

I will let you know if I make any progress about this issue.

Cheers,

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Displaying structure members named like C keywords.

[Sergio Durigan Junior]

On Friday, August 22 2014, Emilio Lopes wrote:

 Would it be possible for you to come up with a simpler reproducer
 and send it to this list?  I am guessing there is something else in
 your code that might be triggering this.

 I was hoping for this to be something simple...  Oh, well.

Yeah, sometimes issues are not so simple...

 As you can imagine this is a somewhat larger codebase, with lots of
 automatically generated code from XML files, using those structures.

Sure, that is also why I asked for a simpler reproducer :-).

 (gdb) p P_SLAVE_CMDS_OPTIONS_HAL_OPTMIN_ENABLED
 $1 = (struct param_t *) 0x10db9c _slave_cmds_options_hal_optmin
 (gdb) set sysroot ~/projects/hal/system/platform-tam3517/root-debug
 Reading symbols from
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libpthread.so.0...done.
 Loaded symbols for
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libpthread.so.0
 Reading symbols from
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/librt.so.1...done.
 Loaded symbols for
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/librt.so.1
 Reading symbols from
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libstdc++.so.6...done.
 Loaded symbols for
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libstdc++.so.6
 Reading symbols from
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libm.so.6...done.
 Loaded symbols for
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libm.so.6
 Reading symbols from
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libgcc_s.so.1...done.
 Loaded symbols for
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libgcc_s.so.1
 Reading symbols from
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libc.so.6...done.
 Loaded symbols for
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/libc.so.6
 Reading symbols from
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/ld-linux.so.3...done.
 Loaded symbols for
 /home/lopes/projects/hal/system/platform-tam3517/root-debug/lib/ld-linux.so.3
 (gdb) p P_SLAVE_CMDS_OPTIONS_HAL_OPTMIN_ENABLED
 A syntax error in expression, near
 `complex.paramv[29].info.complex.paramv[0].info.complex.paramv[1].info.complex.paramv[0])'.
 (gdb) set sysroot ''
 warning: Unable to find dynamic linker breakpoint function.
 GDB will be unable to debug shared library initializers
 and track explicitly loaded dynamic code.
 (gdb) p P_SLAVE_CMDS_OPTIONS_HAL_OPTMIN_ENABLED
 $2 = (struct param_t *) 0x10db9c _slave_cmds_options_hal_optmin
 (gdb)

 Problems come and go as I set/unset `sysroot'!!! (I'm debugging code
 running on an ARM evaluation board remotely.)

Hm, OK, I'm thinking about some issue with symbols here (visibility
maybe).  I made lots of attempts here to reproduce it based on what you
posted, but I still cannot see this behavior using GDB from git HEAD.

If you cannot give more instructions on how to reproduce this, then I
have to ask you to file a bug against GDB on
https://sourceware.org/bugzilla, please.

 Can you give me a hint on what to look for from here?

There are a few debug triggers that you can enable on GDB.  Maybe 'set
debug expression 1' could help.  Also, you can use 'maintenance print
symbols filename' to print all the symbols; this could help analyzing
if 'complex' is being hidden by some other library.  Feel free to post
those things here.

Cheers,

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Potential vulnerabilities in GDB 7.8

[Hádrian R]

Hi, I'm Kaiwaiata​​, since more than 2h searching and finding various
possible vulnerabilities in source code of GDB..
I will tell you one vulnerability now, if they treat me well I will tell
the other..

foolish or important things?

unsafe use of *strcpy()* in *int net_open (.. ..){**:*

*gdb-7.8.tar\gdb\ser-tcp.c:*
*line 187: *strncpy (hostname, name, tmp);
*line 187: *strcpy (hostname, localhost);

*#* if an attacker manages to take control of *hostname[100];*, may cause a
buffer overflow.

*NOTE*: is likely to be directed toward *.bss,* also be a vulnerability

i hope answer, thanks a lot!,
Kaiwaiata - HádrienR.
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Displaying structure members named like C keywords.

[Emilio Lopes]

I'm having trouble trying to display structure members with names like
C keywords.  GDB refuses to display the member called `complex' in
this case.

Here is the structure:

(gdb) p g_global_paramv[37].info
$27 = {
  complex = {
paramc = 20,
paramv = 0xd14f4 _sys_opt
  },
  cmd = {
cmd_fct = 0x14,
wrap = 0xd14f4 _sys_opt
  },
  alias = {
type = 20,
link = 0xd14f4 _sys_opt
  }
}

Printing other members is no problem:

(gdb) p g_global_paramv[37].info.cmd
$28 = {
  cmd_fct = 0x14,
  wrap = 0xd14f4 _sys_opt
}
(gdb) p g_global_paramv[37].info.alias
$29 = {
  type = 20,
  link = 0xd14f4 _sys_opt
}

But trying to print the member `complex' results in an error:

(gdb) p g_global_paramv[37].info.complex
A syntax error in expression, near `complex'.

Note that the error message for non-existing members is different
depending if their names are C keywords (`long' and `int' = syntax
error) or not (`foobar', `xyz' = no member named ...).

(gdb) p g_global_paramv[37].info.foobar
There is no member named foobar.
(gdb) p g_global_paramv[37].info.long
A syntax error in expression, near `long'.
(gdb) p g_global_paramv[37].info.int
A syntax error in expression, near `int'.
(gdb) p g_global_paramv[37].info.xyz
There is no member named xyz.
(gdb)

This happens using gdb-7.8 configured as following:

(gdb) show version
GNU gdb (GDB) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as --host=x86_64-unknown-linux-gnu
--target=arm-cortexa8-linux-gnueabi.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word.
(gdb) show configuration
This GDB was configured as follows:
   configure --host=x86_64-unknown-linux-gnu
--target=arm-cortexa8-linux-gnueabi
 --with-auto-load-dir=$debugdir:$datadir/auto-load
 --with-auto-load-safe-path=$debugdir:$datadir/auto-load
 --with-expat
 --with-gdb-datadir=/usr/local/share/gdb (relocatable)
 --with-jit-reader-dir=/usr/local/lib/gdb (relocatable)
 --without-libunwind-ia64
 --with-lzma
 --with-python=/usr
 --without-guile
 --with-separate-debug-dir=/usr/local/lib/debug (relocatable)
 --with-zlib
 --without-babeltrace

(Relocatable means the directory can be moved with the GDB installation
tree, and GDB will still find it.)

The code was compiled using:

$ arm-cortexa8-linux-gnueabi-gcc --version
arm-cortexa8-linux-gnueabi-gcc (OSELAS.Toolchain-2012.12.1
linaro-4.7-2012.11) 4.7.3 20121106 (prerelease)
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

GDB itself was compiled with:

$ gcc --version
gcc (Debian 4.9.0-7) 4.9.0
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Thank you very much!

 Emílio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Potential vulnerabilities in GDB 7.8

[Sergio Durigan Junior]

On Wednesday, August 20 2014, Hádrian R wrote:

 Hi, I'm Kaiwaiata​​, since more than 2h searching and finding various
 possible vulnerabilities in source code of GDB..
 I will tell you one vulnerability now, if they treat me well I will tell
 the other..

Hello Kaiwaiata,

Thanks for the message.  However, this list is not used by GDB folks
anymore.  I recommend you to post your message on g...@sourceware.org.

 unsafe use of *strcpy()* in *int net_open (.. ..){**:*

 *gdb-7.8.tar\gdb\ser-tcp.c:*
 *line 187: *strncpy (hostname, name, tmp);
 *line 187: *strcpy (hostname, localhost);

You could even post a patch fixing this, if you want.  To do that, send
the patch to gdb-patc...@sourceware.org.

Thanks,

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Displaying structure members named like C keywords.

[Emilio Lopes]

 I could not reproduce the problem here.  Would you mind providing the
 structure declaration, or at least a reproducer?

Hello Sergio,

thank you very much for your prompt answer!

Here is the declaration of the structure:

  typedef struct param_t {
const char*  name;
type_t type;
short not_available : 1;
short rlevel : 4;
short wlevel : 4;
union {
  struct {
void* get_fct;
void* set_fct;
void* gsv_fct;
int32_t polling_default;
int32_t polling_min;
  } natural;
  struct {
unsigned short paramc;
struct param_t* paramv;
  } complex;
  struct {
void (*cmd_fct)();
void (*wrap)(void (*cmd_fct)(), p_id cmd, const variant_t*
argv, size_t argc, variant_t* res);
  } cmd;
  struct {
type_t type;
struct param_t *link;
  } alias;
} info;
struct param_t* parent;
void* user_data;
  } param_t;

  extern param_t* const g_global_paramv;

Regards

 Emílio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

SIGBUS with no backtrace

[徐刚辉]

Here is the output:

(gdb) r
Starting program: /home/root/Data_reporter
[10101.498397] Alignment trap: Data_reporter (1935) PC=0x0fc0 
Instr=0xe1923f9f Address=0x0013000d FSR 0x001

Program received signal SIGBUS, Bus error.
0x0fc0 in ?? ()
(gdb) bt
#0  0x0fc0 in ?? ()



I want to know where cause this bug, but backtrace just give me this.
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

The 64-bit gdb on Solaris can't parse 32-bit core dump file

[Nan Xiao]

Hi, all:


I have reported a issue about gdb: 
https://sourceware.org/bugzilla/show_bug.cgi?id=17045. To be simple, it is the 
64-bit gdb on Solaris can't parse 32-bit core dump file. I also find this issue 
has been reported in 2012:https://sourceware.org/bugzilla/show_bug.cgi?id=14944.


I have tried to analyse the issue, and find the cause:

asection *
bfd_get_section_by_name (bfd *abfd, const char *name)
{
  struct section_hash_entry *sh;


  sh = section_hash_lookup (abfd-section_htab, name, FALSE, FALSE);
  if (sh != NULL)
return sh-section;


  return NULL;
}

static void
core_open (char *filename, int from_tty)
{
..
bfd_map_over_sections (core_bfd, add_to_thread_list,
 bfd_get_section_by_name (core_bfd, .reg));
..
}

The core_open try to get .reg section, and the .reg section doesn't 
exist, but section_hash_lookup doesn't create it.


Then when execute get_core_register_section 
(core_open-post_create_inferior-.-get_core_register_section) function:
static void
get_core_register_section (struct regcache *regcache,
   const char *name,
   int which,
   const char *human_name,
   int required)
{
..
section = bfd_get_section_by_name (core_bfd, section_name);
  if (! section)
{
  if (required)
warning (_(Couldn't find %s registers in core file.),
 human_name);
  return;
}
..
}

Because the .reg section doesn't exist, so the warning will report.

Could anyone help or comment on this issue? Thanks very much!

Best Regards
Nan Xiao___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: How to determine the order of the registers got, their width and count?

[Sergio Durigan Junior]

On Friday, June 06 2014, Ananda Vardhana wrote:

 I am newbie in GDB. I had couple of questions

Hello Ananda,

I don't really have time to answer all of your questions now; I'd
strongly recommend that you send them to g...@sourceware.org, which is
the official mailing list for GDB (this one is just a placeholder).

 1.  When I send out 'g' I get a full dump of the registers. Is there 'q' 
 query packet I can send and ask the GDB server in what order(eax, ebx, ecx 
 ...) will it dump the registers?

AFAIK, no, there isn't.  From the GDB manual:

  Each byte of register data is described by two hex digits. The bytes
  with the register are transmitted in target byte order. The size of
  each register and their position within the ‘g’ packet are determined
  by the GDB internal gdbarch functions DEPRECATED_REGISTER_RAW_SIZE and
  gdbarch_register_name.

So you'd have to check gdbarch_register_name in order to obtain this
information.

 2.  Before we do a 'g' can we tell the server that we are interested in 
 32 bit (EAX, ECX etc ...) only?

I don't think you can.  You can read the registers separately, though.

 3.  Can I send out a 'q' packet and ask the server whether it will give 
 me back 32 or 64 bit registers?

I don't understand this question.  If you're interested in reading some
specific register, you can do that.  Otherwise, using the 'g' packet,
you will obtain all of them.

I'll see if I can answer your other questions when I have more time.

-- 
Sergio
GPG key ID: 65FC5E36
Please send encrypted e-mail if possible
http://blog.sergiodj.net/

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

How to determine the order of the registers got, their width and count?

[Vardhana, Ananda]

I am newbie in GDB. I had couple of questions

1.  When I send out 'g' I get a full dump of the registers. Is there 'q' 
query packet I can send and ask the GDB server in what order(eax, ebx, ecx ...) 
will it dump the registers?

2.  Before we do a 'g' can we tell the server that we are interested in 32 
bit (EAX, ECX etc ...) only?

3.  Can I send out a 'q' packet and ask the server whether it will give me 
back 32 or 64 bit registers?

4.  Nowadays it is mostly 64 bit systems and they support both 32 and 64 
bit. So my idea was to ask whatever I want.

Please check out these transactions:

Sending packet: $qSupported:multiprocess+;xmlRegisters=i386;qRelocInsn+#b5...Ack
Packet received: ReverseStep+;ReverseContinue+;qXfer:features:read+
Packet qSupported (supported-packets) is supported
Sending packet: $Hg0#df...Ack
Packet received: OK
Sending packet: $qXfer:features:read:target.xml:0,283#e8...Ack
Packet received: mtarget version=1.0\n  
architecturei386:x86-64/architecture\n/target\n
Sending packet: $qXfer:features:read:target.xml:4c,283#4f...Ack
Packet received: l

1. Question is how did it come up with the number 0,283
2. What range does 0,283 imply? Is it the number of lines in the target.xml 
file?
3. How can I get the total count?
4. Please see that the next time it does it from 4c,283. Where did it get these 
numbers?
  Packet received: mtarget version=1.0\n  
  architecturei386:x86-64/architecture\n/target\n
5.  I guess architecturei386:x86-64/architecture means the system is an 
Intel system(i386), it supports both 32 bit(x86) and 64 bit (64). Is that right?


Sorry for the long list of questions, just wanted to spill out ... . Many 
thanks in advance

Cheers
 Ananda


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

RE: Usage of vCont packet please

[Vardhana, Ananda]

Hi Sergio,

Thanks for replying. It compiles fine but the server complains with the 
following error:

[gdb0 info] got message: vCont?
[gdb0 info] Sending packet: vCont;c;C;s;S
[gdb0 info] got message: vCont;c:-1
[gdb0 error] Malformed vCont packet ;c:-1, ignoring

I guess the server is dated and I shall see if I can fix the server side. The 
comment for vCont in the GDB website says vCont is new and using H is being 
obsoleted. I did try H and the server liked it. If you have any comments on my 
conlcusion please let me know

Thanks
Ananda

-Original Message-
From: Sergio Durigan Junior [mailto:sergi...@sergiodj.net] 
Sent: Thursday, May 22, 2014 5:34 PM
To: Vardhana, Ananda
Cc: bug-gdb@gnu.org
Subject: Re: Usage of vCont packet please

On Thursday, May 22 2014, Ananda Vardhana wrote:

 Right now I send the packet Hc-1 meaning continue or make the target 
 run and the -1 signifies do it on all process. It works fine.  What 
 would be the equivalent for that in vCont? I do check and vCont?
 Support and the server does support it.

Hello Ananda,

You mean to use vCont to resume all threads of the inferior, right?

 vCont;c-1 does not work and whatever I do with vcont it hangs. The 
 documentation in 
 https://sourceware.org/gdb/onlinedocs/gdb/Packets.html#thread%2did%20s
 yntax

 Does not seem to help or I am misinterpreting.  If you point me to URL 
 with usage, meaning and example if vCont that would be ideal

It should be vCont;c:-1 (note the colon between c and -1).  Could you try 
that?

Thanks,

--
Sergio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Usage of vCont packet please

[Sergio Durigan Junior]

On Monday, May 26 2014, Ananda Vardhana wrote:

 Hi Sergio,

 Thanks for replying. It compiles fine but the server complains with the 
 following error:

 [gdb0 info] got message: vCont?
 [gdb0 info] Sending packet: vCont;c;C;s;S
 [gdb0 info] got message: vCont;c:-1
 [gdb0 error] Malformed vCont packet ;c:-1, ignoring

 I guess the server is dated and I shall see if I can fix the server
 side. The comment for vCont in the GDB website says vCont is new and
 using H is being obsoleted. I did try H and the server liked it. If
 you have any comments on my conlcusion please let me know

Hi Ananda,

Yeah, that may well be the reason.  I don't remember if you provided the
version of GDB, so using an old one is likely to not work with recent
packets, of course :-).  It might be good considering updating the
version, or maybe backport the patch that implemented vCont on
gdbserver.

Anyway, I also wanted to let you know that this mailing list is actually
not the official one of the GDB project.  Unfortunately, it is not
documented anywhere so some people still send email to this list.  For
future questions, please e-mail g...@sourceware.org.

Thanks,

-- 
Sergio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Usage of vCont packet please

[Sergio Durigan Junior]

On Thursday, May 22 2014, Ananda Vardhana wrote:

 Right now I send the packet Hc-1 meaning continue or make the target
 run and the -1 signifies do it on all process. It works fine.  What
 would be the equivalent for that in vCont? I do check and vCont?
 Support and the server does support it.

Hello Ananda,

You mean to use vCont to resume all threads of the inferior, right?

 vCont;c-1 does not work and whatever I do with vcont it hangs. The 
 documentation in
 https://sourceware.org/gdb/onlinedocs/gdb/Packets.html#thread%2did%20syntax

 Does not seem to help or I am misinterpreting.  If you point me to URL with 
 usage, meaning and example if vCont that would be ideal

It should be vCont;c:-1 (note the colon between c and -1).  Could
you try that?

Thanks,

-- 
Sergio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

[guile] Multiple value returns incorrectly printed

[Andy Wingo]

Multiple value returns from Guile should print as multiple values.

Test case:

(gdb) guile (values 1 2)

Expected results:
1
2

Actual results:
#values (1 2)

Additionally I would expect values from Guile to get GDB history
variables ($1, $2, etc), at least if they were convertable to GDB
values.  Perhaps I misunderstand, though.

Andy

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

gdb compilation error

[William A Gueble]

During the compilation of my gdb download, the process terminates after
failing to locate the config.h file. However, several lines before, it is
clear that the config.h file was created, right after the creation of a
Makefile. This occurs during the configuration of ./libdecnumber. I really
need to use this program to help me debug some code for my homework
assignment that is due later today, so I was hoping that you could shed
some light on this error.

Thank You,

Will Gueble
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: gdb compilation error

[Sergio Durigan Junior]

On Sunday, March 30 2014, William A. Gueble wrote:

 During the compilation of my gdb download, the process terminates after
 failing to locate the config.h file. However, several lines before, it is
 clear that the config.h file was created, right after the creation of a
 Makefile. This occurs during the configuration of ./libdecnumber. I really
 need to use this program to help me debug some code for my homework
 assignment that is due later today, so I was hoping that you could shed
 some light on this error.

Hello William,

Without output from your terminal, and descriptions of how you are
compiling GDB, it is very hard to emit some opinion.  You should also
provide information about the system you are running, etc.

Thanks,

-- 
Sergio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Fwd: Wrong date in page

[Abani Kumar Meher]

Hi

January 8th, 2013: *GDB 7.7 branch created *text in
http://www.gnu.org/software/gdb/ page is wrong. I think year is written
wrong here. It is 2014 I think, though I am not sure if that branch was
created last year. It looked odd to me so reported. Please ignore if text
in that page is correct.

Thanks,
-- 

Abani Kumar Meher
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Fwd: Wrong date in page

[Sergio Durigan Junior]

On Thursday, January 30 2014, Abani Kumar Meher wrote:

 January 8th, 2013: *GDB 7.7 branch created *text in
 http://www.gnu.org/software/gdb/ page is wrong. I think year is written
 wrong here. It is 2014 I think, though I am not sure if that branch was
 created last year. It looked odd to me so reported. Please ignore if text
 in that page is correct.

Thanks, the date is indeed wrong, will be fixed soon.

-- 
Sergio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Bug in tracing frames

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

In gdb 7.01-debian, Emacs got into an infloop and I typed C-g C-g to
get back to GDB.  I got the following incomplete backtrace.  Evidently
GDB is unable to trace the stack back properly from the signal
handler.

This is on the Lemote Yeeloong.

Please ack receipt of this message.


#0  0x76a4d3c4 in kill () from /lib/libc.so.6
#1  0x00657004 in sys_suspend () at sysdep.c:450
#2  0x0063fcf8 in handle_interrupt (in_signal_handler=true) at keyboard.c:10318
#3  0x0063fb18 in handle_interrupt_signal (sig=2) at keyboard.c:10259
#4  0x006599b0 in deliver_process_signal (sig=2, 
handler=0x63fa78 handle_interrupt_signal) at sysdep.c:1568
#5  0x0063fb74 in deliver_interrupt_signal (sig=2) at keyboard.c:10266
#6  signal handler called
#7  0x in ?? ()
#8  0x in ?? ()

Lisp Backtrace:
get-text-property (0x7fff09e8)
font-lock-extend-jit-lock-region-after-change (0x7fff0dbc)
run-hook-with-args (0x7fff0db8)
jit-lock-after-change (0x7fff1144)
replace-match (0x7fff1348)
grep-filter (0x7fff1698)
run-hooks (0x7fff1710)
compilation-filter (0x7fff19dc)

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call.


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Bug in tracing frames

[Sergio Durigan Junior]

On Tuesday, January 07 2014, Richard Stallman wrote:

 [[[ To any NSA and FBI agents reading my email: please consider]]]
 [[[ whether defending the US Constitution against all enemies, ]]]
 [[[ foreign or domestic, requires you to follow Snowden's example. ]]]

 In gdb 7.01-debian, Emacs got into an infloop and I typed C-g C-g to
 get back to GDB.  I got the following incomplete backtrace.  Evidently
 GDB is unable to trace the stack back properly from the signal
 handler.

 This is on the Lemote Yeeloong.

 Please ack receipt of this message.


 #0  0x76a4d3c4 in kill () from /lib/libc.so.6
 #1  0x00657004 in sys_suspend () at sysdep.c:450
 #2  0x0063fcf8 in handle_interrupt (in_signal_handler=true) at 
 keyboard.c:10318
 #3  0x0063fb18 in handle_interrupt_signal (sig=2) at keyboard.c:10259
 #4  0x006599b0 in deliver_process_signal (sig=2, 
 handler=0x63fa78 handle_interrupt_signal) at sysdep.c:1568
 #5  0x0063fb74 in deliver_interrupt_signal (sig=2) at keyboard.c:10266
 #6  signal handler called
 #7  0x in ?? ()
 #8  0x in ?? ()

Thanks for the report.

I believe there are two bugs in our bugzilla which are related to this
issue:

https://sourceware.org/bugzilla/show_bug.cgi?id=14506

https://sourceware.org/bugzilla/show_bug.cgi?id=11348

AFAIR, there has been no attempt to fix those yet.

-- 
Sergio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Suggestion for `return'

[Richard Stallman]

The `return' command should set a flag so that `continue' behaves like
`signal 0'.  I know about the need for `signal 0' to avoid crashing,
but just now I forgot it and lost important data.  I think that anyone
who takes the trouble to return out of a stack frame has indicated
a desire to keep running the program rather than let it handle the signal.

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call.


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Bug in entering numbers

[Sergio Durigan Junior]

On Saturday, October 12 2013, Richard Stallman wrote:

 In GDB 7.0.1-debian

 print -2147483648

 outputs

 $1 = 2147483648

 which I think is not right.

Thanks for the report, I will take a look at this when I have time.

You might want to consider opening a bug using
https://sourceware.org/bugzilla/enter_bug.cgi?product=gdb, though.  I
guess I may be the only GDB developer who is subscribed to this list...

Thanks,

-- 
Sergio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Bug in entering numbers

[Richard Stallman]

In GDB 7.0.1-debian

print -2147483648

outputs

$1 = 2147483648

which I think is not right.

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call.


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

C++, linux-gate.so.1, 'set solib-search-path', and 'set sysroot'

[Emanuel Berg]

In gdb, I got this

warning: Could not load shared library symbols for
linux-gate.so.1. Do you need set solib-search-path or set
sysroot?

I compiled with

g++ -I include/ -ggdb *.cpp -o run

uname -a tells me

Linux nl106-137-194 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686
GNU/Linux

What does it mean?
-- 
Emanuel Berg - programmer (hire me! CV below)
computer projects: http://user.it.uu.se/~embe8573
internet activity: http://home.student.uu.se/embe8573
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: C++, linux-gate.so.1, 'set solib-search-path', and 'set sysroot'

[Sergio Durigan Junior]

On Friday, August 30 2013, Emanuel Berg wrote:

 In gdb, I got this

 warning: Could not load shared library symbols for
 linux-gate.so.1. Do you need set solib-search-path or set
 sysroot?

 I compiled with

 g++ -I include/ -ggdb *.cpp -o run

 uname -a tells me

Hi,

There is a bug filed against GDB about this issue, and there is also a
workaround posted to the mailing list, though it has not been accepted
yet.  You can take a look at the bug at:

https://sourceware.org/bugzilla/show_bug.cgi?id=14466

and subscribe yourself to it, or ask for more details.

This list (bug-gdb@gnu.org) is not really used anymore, so I suggest
that you follow the bug above and send questions to
g...@sourceware.org.

Thanks!

-- 
Sergio

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Problem Breakpoint

[Fox Fossati]

Hi! I have a problem with GDB and i don't know if is a bug or maybe i made
a mistake
I'm using the last GDB 7.6 on Linux Mint Debian and i'm tryng some easy
example of cpuid from the book:
Professional Assembly Language of Richard Blum.

The problem is that when i put a breakpoint after the nop instruction, for
example
break *_start+1
and then i run the program, i have this error:

Warning:
Cannot insert breakpoint 1.
Error accessing memory address : Input/output error.

If i run without breakpoints the program ends end exit without problems
so...i think there isnt any error
in the code that i copyied and pasted from the book.

Thanks a lot for your help and greetings from italy.
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Broken link on the GDB webpage

[Erik Carstensen]

Hi,

The page:
http://www.gnu.org/software/gdb/documentation/
contains a link to Debugging with GDB:
http://shop.fsf.org/product/debugging-gdb-gnu-source-level-debugger/
which is broken. It should be:
http://shop.fsf.org/product/debugging-gdb-gnu-source-level-debugger-10/
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: GDB m68k debug multi-thread application fails: capability not available

[lars71dk]

Den onsdag den 29. maj 2013 01.16.51 UTC+2 skrev john@gmail.com:
 Lars - I realize this is a very old post but I am wondering if you ever 
 figured this out.  I am running into the same problem and have found very, 
 very little on the web that is useful.  Any insight you can add would be most 
 appreciated.
 

Hi John,

Here is a patch for gdb 6.6 that fixed the problem for me. There are two 
patches, and below is the spec file I used (with Freescale ltib and kernel 
2.6.29).

Regards,
Lars


---
%define pfx /opt/freescale/rootfs/%{_target_cpu}
%define cs_version 4.2-82

Summary : Gdb - GNU Source level debugger for C, C++
Name: gdb
Version : 6.6
Release : 2
License : GPL
Vendor  : Freescale
Packager: Stuart Hughes/Steve Papacharalambous
Group   : Development/Debuggers
Source  : %{name}-%{version}.tar.gz
Patch0  : gdb-6.0-tcsetpgrp.patch
Patch1  : %{name}-%{cs_version}-from-fsf-6_6.diff.gz
Patch2  : %{name}-%{version}-UPAGES-undefined.patch
BuildRoot   : %{_tmppath}/%{name}
Prefix  : %{pfx}

%Description
%{summary}

Notes:

This gdb package is built using gdb-6.6 plus the gdb patch from the
CodeSourcery %{cs_version} release: gdb-%{cs_version}-from-fsf-6_6.diff

The gdb tarball can be obtained from any of the GNU ftp sites or their mirrors.
The CodeSourcery patch can be obtained by downloading the source rpm:
freescale-powerpc-linux-gnu-%{cs_version}.src.rpm from:
http://www.codesourcery.com/gnu_toolchains/power/download.html and then
extracting the gdb patch from this source rpm.

requires: libtermcap and ncurses


%Prep
%setup
%patch0 -p1
%patch1 -p1
%patch2 -p1

# Temporary hack.  Stevep
# This is to prevent the following error occuring on some build systems:
# [snip]
# Doing pdf in readline
# make[3]: Entering directory 
`/home/stevep/work/ltib/rpm/BUILD/gdb-6.6/readline'
# ( cd doc  make -w pdf )
# make[4]: Entering directory 
`/home/stevep/work/ltib/rpm/BUILD/gdb-6.6/readline/doc'
# TEXINPUTS=.:../.././readline/doc:$TEXINPUTS ../.././readline/doc/texi2dvi 
../.././readline/doc/rlman.texi
# This is TeX, Version 3.14159 (Web2C 7.3.1)
# (/home/stevep/work/ltib/rpm/BUILD/gdb-6.6/readline/doc/rlman.texi
# (/usr/share/texmf/tex/texinfo/texinfo.tex
# Loading texinfo [version 1999-09-25.10]: Basics, pdf, fonts, page headings,
# tables, conditionals, indexing, sectioning, toc, environments, defuns, macros,
# cross references, (/usr/share/texmf/tex/plain/dvips/epsf.tex) localization,
# and turning on texinfo input format.) (rlman.aux) (version.texi)
# ! Undefined control sequence.
# l.11 @copying
#  
# ? 
# [/snip]
perl -pi.orig -e 's,^\@copying,\@comment \@copying,;
  s,^\@end\s+copying,\@comment \@end copying,;
  s,^\@insertcopying,\@comment \@insertcopying,;' 
readline/doc/rlman.texi

perl -pi.orig -e 's,^\@copying,\@comment \@copying,;
  s,^\@end\s+copying,\@comment \@end copying,;
  s,^\@insertcopying,\@comment \@insertcopying,;' 
readline/doc/history.texi

perl -pi.orig -e 's,^\@copying,\@comment \@copying,;
  s,^\@end\s+copying,\@comment \@end copying,;
  s,^\@insertcopying,\@comment \@insertcopying,;' 
readline/doc/rluserman.texi


%Build
ORIG_PATH=$PATH
# This is the optimised host type.  Needed to prevent infering a native build
OPT_CFGHOST=`echo ${TOOLCHAIN_PREFIX} | perl -n -e 's,-$,,;print'`


# Ensure that build is never the same as hostA.
GDB_BUILD=`echo %{_build} | sed s/-/-build_/`

# Set up the host rpm command.  This is done so that the version of expat
# on the host system can be determined.  This is needed for cross-gdb with
# xml support enabled.
if [ -x /bin/rpm ]
then
HOST_RPM=/bin/rpm
elif [ -x /usr/bin/rpm ]
then
HOST_RPM=/usr/bin/rpm
else
HOST_RPM=
fi

# Get the version of the host expat package and determine whether it is
# too old to provide cross-gdb xml support.
# Sigh, this is very ugly!
if [ -n ${HOST_RPM} ]
then
HOST_EXPAT_VER=`${HOST_RPM} -q expat | perl -p -e 's,expat-(.*)-\d+$,$1,'`
HOST_EXPAT_VER1=`echo ${HOST_EXPAT_VER} | cut -d. -f1`
HOST_EXPAT_VER2=`echo ${HOST_EXPAT_VER} | cut -d. -f2`
HOST_EXPAT_VER3=`echo ${HOST_EXPAT_VER} | cut -d. -f3`

# Starting with the first compare each of the host expat version numbers
# with the mimimum required.  Not pretty!!
if [ ${HOST_EXPAT_VER1} -gt 1 ]
then
HOST_EXPAT_TOO_OLD=no
elif [ ${HOST_EXPAT_VER1} -eq 1 ]
then
if [ ${HOST_EXPAT_VER2} -gt 95 ]
then
HOST_EXPAT_TOO_OLD=no
elif [ ${HOST_EXPAT_VER2} -eq 95 ]
then
if [ ${HOST_EXPAT_VER3} -ge 5 ]
then
HOST_EXPAT_TOO_OLD=no
else
   HOST_EXPAT_TOO_OLD=yes
fi
else
HOST_EXPAT_TOO_OLD=yes
fi
else
HOST_EXPAT_TOO_OLD=yes
fi
else
# Failed to get 

Re: GDB m68k debug multi-thread application fails: capability not available [PATCH 2/2] gdb-6.6-UPAGES-undefined.patch

[lars71dk]

diff -rupaN gdb-6.6-orig/bfd/hosts/m68klinux.h gdb-6.6/bfd/hosts/m68klinux.h
--- gdb-6.6-orig/bfd/hosts/m68klinux.h  2010-08-09 13:28:14.0 +0800
+++ gdb-6.6/bfd/hosts/m68klinux.h   2010-08-09 13:30:28.0 +0800
@@ -20,6 +20,12 @@
 /* Linux dumps struct task_struct at the end of the core-file.  This
structure is currently 2512 bytes long, but we allow up to 4096
bytes to allow for some future growth.  */
+
+#define NBPG 4096
+#define UPAGES 1
+#define HOST_TEXT_START_ADDR (u.start_code)
+#define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG)
+
 #define TRAD_CORE_EXTRA_SIZE_ALLOWED   4096
 #define TRAD_UNIX_CORE_FILE_FAILING_SIGNAL(abfd) \
   ((abfd)-tdata.trad_core_data-u.signal)
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: GDB m68k debug multi-thread application fails: capability not available [PATCH 1/2] gdb-6.6-m68k-pthread.patch

[lars71dk]

Add the ps_get_thread_area function to m68k to provide debugging of
programs linked to libpthread. The code was copied from the MIPS
implementations in gdb and gdbserver.

diff -ur gdb-6.6.orig/gdb/gdbserver/linux-m68k-low.c 
gdb-6.6/gdb/gdbserver/linux-m68k-low.c
--- /home/davidw/tmp/gdb-6.6.orig/gdb/gdbserver/linux-m68k-low.c
2011-06-23 09:09:53.977584261 -0500
+++ gdb-6.6/gdb/gdbserver/linux-m68k-low.c  2011-06-23 09:44:41.434490495 
-0500
@@ -153,6 +153,26 @@
   return 0;
 }
 
+#include asm/ptrace.h
+#include gdb_proc_service.h
+
+/* Fetch the thread-local storage pointer for libthread_db.  */
+
+ps_err_e
+ps_get_thread_area (const struct ps_prochandle *ph,
+lwpid_t lwpid, int idx, void **base)
+{
+  if (ptrace (PTRACE_GET_THREAD_AREA, lwpid, NULL, base) != 0)
+return PS_ERR;
+
+  /* IDX is the bias from the thread pointer to the beginning of the
+ thread descriptor.  It has to be subtracted due to implementation
+ quirks in libthread_db.  */
+  *base = (void *) ((char *)*base - idx);
+
+  return PS_OK;
+}
+
 struct linux_target_ops the_low_target = {
   m68k_num_regs,
   m68k_regmap,
diff -ur gdb-6.6.orig/gdb/m68klinux-nat.c gdb-6.6/gdb/m68klinux-nat.c
--- /home/davidw/tmp/gdb-6.6.orig/gdb/m68klinux-nat.c   2011-06-23 
09:09:54.167562142 -0500
+++ gdb-6.6/gdb/m68klinux-nat.c 2011-06-23 09:41:10.319081266 -0500
@@ -67,6 +67,26 @@
   45, 46, 47
 };
 
+#include asm/ptrace.h
+#include gdb_proc_service.h
+
+/* Fetch the thread-local storage pointer for libthread_db.  */
+
+ps_err_e
+ps_get_thread_area (const struct ps_prochandle *ph,
+lwpid_t lwpid, int idx, void **base)
+{
+  if (ptrace (PTRACE_GET_THREAD_AREA, lwpid, NULL, base) != 0)
+return PS_ERR;
+
+  /* IDX is the bias from the thread pointer to the beginning of the
+ thread descriptor.  It has to be subtracted due to implementation
+ quirks in libthread_db.  */
+  *base = (void *) ((char *)*base - idx);
+
+  return PS_OK;
+}
+
 /* Which ptrace request retrieves which registers?
These apply to the corresponding SET requests as well.  */
 #define NUM_GREGS (18)
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: GDB m68k debug multi-thread application fails: capability not available

[john . canosa]

Lars - I realize this is a very old post but I am wondering if you ever figured 
this out.  I am running into the same problem and have found very, very little 
on the web that is useful.  Any insight you can add would be most appreciated.
Regards,
John

On Friday, January 14, 2011 7:37:12 AM UTC-5, Horvath, Lars Michael wrote:
 Hello,
 
 
 On
 a ColdFire (twr-mcf5441x) board, I am trying to debug an application linked
 with -lpthread, but GDB fails:
 
 
 Starting
 program: /upcodepr.linux.mcf54415
 
 Reading symbols
 from /lib/ld.so.1...done.
 
 Reading symbols
 from /lib/libc.so.6...done.
 
 Reading symbols
 from /lib/libpthread.so.0...done.
 
 [Thread debugging using libthread_db enabled]
 
 Reading symbols
 from /lib/librt.so.1...done.
 
 [New Thread 0x60180210 (LWP 621)]
 
 [New Thread 0x609814c0 (LWP 624)]
 
 Cannot find
 user-level thread for LWP 621: capability not available
 
 
 I
 am using the Freescale ltib package to build the kernel (2.6.29).
 
 
 GCC
 is gcc-4.4.54-eglibc-2.10.54
 
 
 GDB
 version is 6.6.50.20070821-cvs
 
 
 The
 application was linked against the glibc included in the tool chain, and the
 same glibc is included on the target. The library files exist and have the 
 same
 dates so I assume they are in sync. Also, they are not stripped.
 
 
 Single
 threaded apps. can be loaded and debugged ok.
 
 
 Any
 help on how to make GDB find user level threads is appreciated!
 
 
 Regards,
 
 
 -
 Lars
 
 
  
 
 
 
 
 
 
 
 
 
 
 Please be advised that this email may contain confidential 
 
 information.  If you are not the intended recipient, please notify us 
 
 by email by replying to the sender and delete this message.  The 
 
 sender disclaims that the content of this email constitutes an offer 
 
 to enter into, or the acceptance of, any agreement; provided that the 
 
 foregoing does not invalidate the binding effect of any digital or 
 
 other electronic reproduction of a manual signature that is included 
 
 in any attachment.

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: gdb 7.5.91 resolves symbolic links when passing argv[0]

[Pedro Alves]

Hello David,

On 04/28/2013 10:14 AM, David Kastrup wrote:
 
 I've reported this to the Ubuntu bug tracker, but judging from the
 package files, I can't find proof that it has been introduced
 downstream.

I'm afraid that issues reported on this list often end up
ignored/forgotten.  I'm not exactly sure why we still have it.
Could you report this to the upstream bug tracker?  It's at:

 http://sourceware.org/bugzilla/

Sorry for the extra trouble.

Thanks,
-- 
Pedro Alves


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Old rs6000-tdep unwind bug still there in 7.5.1

[Pedro Alves]

Hi Douglas,

On 04/25/2013 11:20 PM, Douglas Graham wrote:
 The bug described here:
 
 http://lists.gnu.org/archive/html/bug-gdb/2011-08/msg0.html

I'm afraid that issues reported on this list often end up
ignored/forgotten.  Could you report this to the upstream bug
tracker?  It's at:

 http://sourceware.org/bugzilla/

Or better even, post a patch upstream?  Here are the contribution
instructions:

  http://sourceware.org/gdb/contribute/

Marc Khouzam @ Ericsson may be able to help you with it, given
he has copyright assignment on file, often works with us gdb
folks, and has repository access.  (Though it sounds like the fix
would be small enough to not require copyright assignment.)

Thanks,
-- 
Pedro Alves


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: gdb 7.5.91 resolves symbolic links when passing argv[0]

[David Kastrup]

Pedro Alves pal...@redhat.com writes:

 Hello David,

 On 04/28/2013 10:14 AM, David Kastrup wrote:
 
 I've reported this to the Ubuntu bug tracker, but judging from the
 package files, I can't find proof that it has been introduced
 downstream.

 I'm afraid that issues reported on this list often end up
 ignored/forgotten.  I'm not exactly sure why we still have it.
 Could you report this to the upstream bug tracker?  It's at:

  http://sourceware.org/bugzilla/

 Sorry for the extra trouble.

I have not been able to figure out all the right categories: the tracker
is completely befuddling to me.  That's why I reverted to the list
instead of registering on yet-another-website for just a single use
which I'd probably get wrong anyway.

I have verified that the problem is still present in current master
(checking out the git mirror).  I have not been able to figure out just
when it has been introduced, and I don't have a clue where to look in
the code (the obvious grep for readlink did not really succeed in
letting me find a suspect).

-- 
David Kastrup

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: gdb 7.5.91 resolves symbolic links when passing argv[0]

[Pedro Alves]

On 04/29/2013 11:36 AM, David Kastrup wrote:

 I have not been able to figure out all the right categories: the tracker
 is completely befuddling to me.  That's why I reverted to the list
 instead of registering on yet-another-website for just a single use
 which I'd probably get wrong anyway.

Fair enough.

I've filed it for you:

http://sourceware.org/bugzilla/show_bug.cgi?id=15415

-- 
Pedro Alves


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

gdb 7.5.91 resolves symbolic links when passing argv[0]

[David Kastrup]

I've reported this to the Ubuntu bug tracker, but judging from the
package files, I can't find proof that it has been introduced
downstream.

The Ubuntu problem description is at
URL:https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1173562.  I
copy the description and example here:

Calling gdb on an executable that is a symbolic link will pass the
target of the symbolic link rather than the specified link as
argv[0] to the program.

As a result, if the program relies on the contents of argv[0] (for
example, for figuring out paths relative to the executable or making
decisions based on the name the executable has been called under),
debugging fails.

Here is an example for a program relying on its argv[0] name:
/usr/bin/latex is a symbolic link to /usr/bin/pdftex, and pdftex loads a
format depending on the name under which it has been called. As a
result,

latex '\stop'

will load the latex.fmt format and finish processing while the same will
fail under gdb since argv[0] is being passed as /usr/bin/pdftex instead
of /usr/bin/latex:

dak@lola:/tmp$ latex '\stop'
This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/Debian)
 restricted \write18 enabled.
entering extended mode
LaTeX2e 2011/06/27
Babel v3.8m and hyphenation patterns for english, dumylang, nohyphenation, bu
lgarian, ukrainian, russian, loaded.
No pages of output.
Transcript written on texput.log.

dak@lola:/tmp$ gdb latex
GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as i686-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/pdftex...(no debugging symbols found)...done.
(gdb) run '\stop'
Starting program: /usr/bin/pdftex '\stop'
This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/Debian)
 restricted \write18 enabled.
entering extended mode
! Undefined control sequence.
 
* \stop

?


Thanks for caring!

-- 
David Kastrup

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Old rs6000-tdep unwind bug still there in 7.5.1

[Douglas Graham]

The bug described here:

http://lists.gnu.org/archive/html/bug-gdb/2011-08/msg0.html

still exists in 7.5.1

--Doug

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: GDB all VERSION

[Pedro Alves]

On 02/01/2013 10:04 PM, sfddfsd wrote:
 view the stack with x/8x $esp .
 
 0xb960:0x080484e00xbbb10x0804846b0xb7fc4ff4
 0xb970:0x080484600x0xb9f80xb7e96e16
 
 and print the string with value proof 0xbbb1 .
 
 (gdb)x/s 0xbbb1
 0xbbb1:proof
 
 print the newly the stack with x/8x $esp and the result is.
 
 0xb960:0xe00x840x040x080xb10xfb0xff0xbf
 
 do you understand ??, this bug is in all version of gdb .

 (gdb) help x
 Examine memory: x/FMT ADDRESS.
 ADDRESS is an expression for the memory address to examine.
 FMT is a repeat count followed by a format letter and a size letter.
 Format letters are o(octal), x(hex), d(decimal), u(unsigned decimal),
   t(binary), f(float), a(address), i(instruction), c(char) and s(string).
 Size letters are b(byte), h(halfword), w(word), g(giant, 8 bytes).
 The specified number of objects of the specified size are printed
 according to the format.

 Defaults for format and size letters are those previously used.
 ^^^
 Default count is 1.  Default address is following last thing printed
 with this command or print.

The manual says:

 Each time you specify a unit size with @code{x}, that size becomes the
 default unit the next time you use @code{x}.  For the @samp{i} format,
 the unit size is ignored and is normally not written.  For the @samp{s} format,
^^^
 the unit size defaults to @samp{b}, unless it is explicitly given.
 ^
 Use @kbd{x /hs} to display 16-bit char strings and @kbd{x /ws} to display
 32-bit strings.  The next use of @kbd{x /s} will again display 8-bit strings.
  ^^^
 Note that the results depend on the programming language of the
 current compilation unit.  If the language is C, the @samp{s}
 modifier will use the UTF-16 encoding while @samp{w} will use
 UTF-32.  The encoding is set by the programming language and cannot
 be altered.

So x/s implicitly sets size to 'b'.  So after x/s, the previously
used size is 'b', and your x/8x $esp becomes equivalent to
x/8xb $esp.  Use x/8xw $esp to get back the previous output.

-- 
Pedro Alves


___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

GDB all VERSION

[sfddfsd]

hi, I write for the tool gdb, this has a bug.
you should compile this code with gcc proof.c -o proof .

#include stdio.h

int main(int argc,char** argv)
{
if( argc == 2 )
{
printf(%s,argv[1]);
}
return 0;
}


the next step is run gdb -q proof and put a breakpoint in function printf.

the direction of prinf is

   0x0804843e +34:call   0x8048300 printf@plt

and put break in 0x0804843e , then should run gdb -q proof.

view the stack with x/8x $esp .

0xb960:0x080484e00xbbb10x0804846b0xb7fc4ff4
0xb970:0x080484600x0xb9f80xb7e96e16

and print the string with value proof 0xbbb1 .

(gdb)x/s 0xbbb1
0xbbb1:proof

print the newly the stack with x/8x $esp and the result is.

0xb960:0xe00x840x040x080xb10xfb0xff0xbf

do you understand ??, this bug is in all version of gdb .

will wait for you answer,please.
regards.

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Problem with user defined commands

[Mohanasundaram Chandran]

Hi All, User defined commands gets messed up if a definition has a name 
starting with ws and called from another definition. Is it a known defect? 
Any workarounds? bash-3.2$ cat test.gdb
define wsbaz
printf wsbaz\n
enddefine foo
wsbaz
enddefine bar
printf bar\n
end bash-3.2$ ./gdb
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-unknown-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) source ./test.gdb
(gdb) foo
warning: Invalid control type in canned commands structure.
warning: Error executing canned sequence of commands.
(gdb) bar
Undefined command: bar.  Try help.
(gdb) show user foo
User command foo:
  wsfoo
  end
  define bar
  printf bar\n(gdb) show user bar
Undefined command: bar.  Try help.
(gdb) show user wsfoo
User command wsfoo:
  printf wsfoo\n(gdb) wsfoo
wsfoo
(gdb)
Cheers,Mohan. ___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

RE: Problem with user defined commands

[Mohanasundaram Chandran]

A small correction in the test.gdb file which I pasted earlier. This is the 
correct one... bash-3.2$ cat test.gdb
define wsfoo
printf wsfoo\n
end
define foo
wsfoo
end
define bar
printf bar\n
end
 From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:18:25 +0530




Hi All,
 
User defined commands gets messed up if a definition has a name starting with 
ws and called from another definition. Is it a known defect? Any workarounds?
 
bash-3.2$ cat test.gdb
define wsbaz
printf wsbaz\n
end
define foo
wsbaz
end
define bar
printf bar\n
end
 
bash-3.2$ ./gdb
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-unknown-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) source ./test.gdb
(gdb) foo
warning: Invalid control type in canned commands structure.
warning: Error executing canned sequence of commands.
(gdb) bar
Undefined command: bar.  Try help.
(gdb) show user foo
User command foo:
  wsfoo
  end
  define bar
  printf bar\n
(gdb) show user bar
Undefined command: bar.  Try help.
(gdb) show user wsfoo
User command wsfoo:
  printf wsfoo\n
(gdb) wsfoo
wsfoo
(gdb)

Cheers,
Mohan.
 
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  ___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

RE: Problem with user defined commands

[Mohanasundaram Chandran]

Another info...this works in gdb 6.5 but not working in 7.2 and 7.5.1 which I 
tried...
 From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: RE: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:22:02 +0530




A small correction in the test.gdb file which I pasted earlier. This is the 
correct one...
 
bash-3.2$ cat test.gdb
define wsfoo
printf wsfoo\n
end
define foo
wsfoo
end
define bar
printf bar\n
end
 
From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:18:25 +0530




Hi All,
 
User defined commands gets messed up if a definition has a name starting with 
ws and called from another definition. Is it a known defect? Any workarounds?
 
bash-3.2$ cat test.gdb
define wsbaz
printf wsbaz\n
end
define foo
wsbaz
end
define bar
printf bar\n
end
 
bash-3.2$ ./gdb
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-unknown-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) source ./test.gdb
(gdb) foo
warning: Invalid control type in canned commands structure.
warning: Error executing canned sequence of commands.
(gdb) bar
Undefined command: bar.  Try help.
(gdb) show user foo
User command foo:
  wsfoo
  end
  define bar
  printf bar\n
(gdb) show user bar
Undefined command: bar.  Try help.
(gdb) show user wsfoo
User command wsfoo:
  printf wsfoo\n
(gdb) wsfoo
wsfoo
(gdb)

Cheers,
Mohan.
 
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  ___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

RE: Problem with user defined commands

[Mohanasundaram Chandran]

We figured that the problematic code was this
  /* Check for while, if, break, continue, etc and build a new
 command line structure for them.  */
  if ((p_end - p = 14  !strncmp (p, while-stepping, 14))
  || (p_end - p = 8  !strncmp (p, stepping, 8))
  || (p_end - p = 2  !strncmp (p, ws, 2)))
 From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: RE: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:30:21 +0530




Another info...this works in gdb 6.5 but not working in 7.2 and 7.5.1 which I 
tried...
 
From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: RE: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:22:02 +0530




A small correction in the test.gdb file which I pasted earlier. This is the 
correct one...
 
bash-3.2$ cat test.gdb
define wsfoo
printf wsfoo\n
end
define foo
wsfoo
end
define bar
printf bar\n
end
 
From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:18:25 +0530




Hi All,
 
User defined commands gets messed up if a definition has a name starting with 
ws and called from another definition. Is it a known defect? Any workarounds?
 
bash-3.2$ cat test.gdb
define wsbaz
printf wsbaz\n
end
define foo
wsbaz
end
define bar
printf bar\n
end
 
bash-3.2$ ./gdb
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-unknown-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) source ./test.gdb
(gdb) foo
warning: Invalid control type in canned commands structure.
warning: Error executing canned sequence of commands.
(gdb) bar
Undefined command: bar.  Try help.
(gdb) show user foo
User command foo:
  wsfoo
  end
  define bar
  printf bar\n
(gdb) show user bar
Undefined command: bar.  Try help.
(gdb) show user wsfoo
User command wsfoo:
  printf wsfoo\n
(gdb) wsfoo
wsfoo
(gdb)

Cheers,
Mohan.
 
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  ___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

RE: Problem with user defined commands

[Mohanasundaram Chandran]

Forgot to mention the file /gdb/cli/cli-script.c
 From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: RE: Problem with user defined commands
Date: Wed, 30 Jan 2013 17:35:40 +0530




We figured that the problematic code was this

  /* Check for while, if, break, continue, etc and build a new
 command line structure for them.  */
  if ((p_end - p = 14  !strncmp (p, while-stepping, 14))
  || (p_end - p = 8  !strncmp (p, stepping, 8))
  || (p_end - p = 2  !strncmp (p, ws, 2)))

 
From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: RE: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:30:21 +0530




Another info...this works in gdb 6.5 but not working in 7.2 and 7.5.1 which I 
tried...
 
From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: RE: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:22:02 +0530




A small correction in the test.gdb file which I pasted earlier. This is the 
correct one...
 
bash-3.2$ cat test.gdb
define wsfoo
printf wsfoo\n
end
define foo
wsfoo
end
define bar
printf bar\n
end
 
From: mohanasundaram.subscr...@outlook.com
To: bug-gdb@gnu.org
Subject: Problem with user defined commands
Date: Wed, 30 Jan 2013 16:18:25 +0530




Hi All,
 
User defined commands gets messed up if a definition has a name starting with 
ws and called from another definition. Is it a known defect? Any workarounds?
 
bash-3.2$ cat test.gdb
define wsbaz
printf wsbaz\n
end
define foo
wsbaz
end
define bar
printf bar\n
end
 
bash-3.2$ ./gdb
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-unknown-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) source ./test.gdb
(gdb) foo
warning: Invalid control type in canned commands structure.
warning: Error executing canned sequence of commands.
(gdb) bar
Undefined command: bar.  Try help.
(gdb) show user foo
User command foo:
  wsfoo
  end
  define bar
  printf bar\n
(gdb) show user bar
Undefined command: bar.  Try help.
(gdb) show user wsfoo
User command wsfoo:
  printf wsfoo\n
(gdb) wsfoo
wsfoo
(gdb)

Cheers,
Mohan.
 
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb  
  ___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Remove personal data from www.mail-archive.com/bug-gdb@gnu.org/msg00341.html

[FUSTER LORIENTE, BEATRIZ (BEATRIZ)]

Please, remove my complete name (Beatriz Fuster Loriente) from 
www.mail-archive.com/bug-gdb@gnu.org/msg00341.html or remove complete message 
if not possible to remove details inside the email. I don't want to be googled 
with my email. I hope you understand the privacy issues.

Thanks a lot,

Beatriz Fuster Loriente




___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

error while configure in gdb

[hiren sangani]

 Dear Contact Person,

 I am trying to connect GDB-7.5.50-1 to the target but I am getting an error

 Configuring in ./libiberty
 configure: loading cache ./config.cache
 configure: error: cannot find install-sh, install.sh, or shtool in ./../..
././../..
 Makefile:6757: recipe for target `configure-libiberty' failed
 make[1]: *** [configure-libiberty] Error 1
 make[1]: Leaving directory `/usr/src/gdb-7.5.50-1'
 Makefile:851: recipe for target `all' failed
 make: *** [all] Error 2

 So if anyone has some suggestion then please post it...I am using cygwin
 environment...

-- 

Mit freundlichen Grüßen / With Best Regards

Hiren
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Types table size and format in the .gcc_exception_table

[alam_shahid]

As part of my research I am updating the .gcc_exception_table of a binary 64 
bit elf file. For small C++ programs that throw exceptions it works OK, but for 
large benchmark programs it's not working. My question is does GCC stores more 
than one table inside the .gcc_exception_table section of the elf file. If it 
does what's the exact format of these tables. I have some knowledge of the 
action table, action records and types table. I am not clear about the size of 
the types table.

I am parsing the tables in this section but is not able to know the exact size 
and format of the types tables, where a pointer to the exception information is 
stored. I need to update this pointer to the new updated location.

Any help is appreciated.
Thanks,
-- Shahid
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: warnings with cvs texinfo version

[Patrice Dumas]

Hello,

Here is an additional patch that takes care of a new warning:
./gdb.texinfo:31: warning: @syncodeindex leads to a merging of fn in itself, 
ignoring

It simply comments out the line 
  @syncodeindex fn fn
which is a bit weird.

On Wed, Jun 20, 2012 at 10:37:53PM +0200, Patrice Dumas wrote:
 Hello,
 
 The following warnings remain when using the cvs makeinfo version.  It
 is unclear to me how to solve these, but hipefully, you should be able
 to fix them, or bear with warnings:
 
 ./gdb.texinfo:22939: warning: @table has text but no @item

These warnings are still there, but now to do what you wanted to do 
with that construct, that is an indented environment without 
anything else special, we added @indentedblock (and @smallindentedblock), 
so I think that you could use that instead of an empty table.

 ./gdb.texinfo:35330: warning: @item missing argument

This warning is also still present.  Here you can use, for example 
@w{} but it will still be a rather dubious construct. 

The other warnings have been removed.

-- 
Pat
Index: gdb/doc/gdb.texinfo
===
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.1039
diff -u -3 -p -r1.1039 gdb.texinfo
--- gdb/doc/gdb.texinfo 2 Jan 2013 15:00:34 -   1.1039
+++ gdb/doc/gdb.texinfo 5 Jan 2013 01:42:19 -
@@ -28,7 +28,7 @@
 @c readline appendices use @vindex, @findex and @ftable,
 @c annotate.texi and gdbmi use @findex.
 @syncodeindex vr fn
-@syncodeindex fn fn
+@c @syncodeindex fn fn
 
 @c !!set GDB manual's edition---not the same as GDB version!
 @c This is updated by GNU Press.
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Program received signal SIGFPE, Arithmetic exception

[Alexandre Furlan]

Hi.

I have the program a FORTRAN90 and when I debug with gdb, is shown

Program received signal SIGFPE, Arithmetic exception.
0x004060be in MAIN__ ()

How to find the line where the error was found ?

Thanks 
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Program received signal SIGFPE, Arithmetic exception

[Eli Zaretskii]

 Date: Tue, 27 Nov 2012 09:01:39 -0800 (PST)
 From: Alexandre Furlan alexandrepfur...@gmail.com
 
 I have the program a FORTRAN90 and when I debug with gdb, is shown
 
 Program received signal SIGFPE, Arithmetic exception.
 0x004060be in MAIN__ ()
 
 How to find the line where the error was found ?

Did you try typing bt, short for backtrace?

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Program received signal SIGFPE, Arithmetic exception

[Eli Zaretskii]

 Date: Tue, 27 Nov 2012 16:14:04 -0200 (BRST)
 From: alexandrepfurlan alexandrepfur...@gmail.com
 cc: Alexandre Furlan alexandrepfur...@gmail.com, bug-gdb@gnu.org
 
 
 I tried, and the result is
 
 Program received signal SIGFPE, Arithmetic exception.
 0x004060be in MAIN__ ()
 (gdb) bt
 #0  0x004060be in MAIN__ ()
 
 And now ?

Did you compile with -g?  It looks like there are no debug info in
this executable.

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Program received signal SIGFPE, Arithmetic exception

[alexandrepfurlan]

Yes. I use

gfortran -g program.f90

I'll try again.

On Tue, 27 Nov 2012, Eli Zaretskii wrote:


Date: Tue, 27 Nov 2012 16:14:04 -0200 (BRST)
From: alexandrepfurlan alexandrepfur...@gmail.com
cc: Alexandre Furlan alexandrepfur...@gmail.com, bug-gdb@gnu.org


I tried, and the result is

Program received signal SIGFPE, Arithmetic exception.
0x004060be in MAIN__ ()
(gdb) bt
#0  0x004060be in MAIN__ ()

And now ?


Did you compile with -g?  It looks like there are no debug info in
this executable.



___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: Program received signal SIGFPE, Arithmetic exception

[alexandrepfurlan]

I tried, and the result is

Program received signal SIGFPE, Arithmetic exception.
0x004060be in MAIN__ ()
(gdb) bt
#0  0x004060be in MAIN__ ()

And now ?


On Tue, 27 Nov 2012, Eli Zaretskii wrote:


Date: Tue, 27 Nov 2012 09:01:39 -0800 (PST)
From: Alexandre Furlan alexandrepfur...@gmail.com

I have the program a FORTRAN90 and when I debug with gdb, is shown

Program received signal SIGFPE, Arithmetic exception.
0x004060be in MAIN__ ()

How to find the line where the error was found ?


Did you try typing bt, short for backtrace?



___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

GDB seg fault

[Amey Desai]

Hello,


I'm new to gdb. I was debugging one of my school assignments in emacs with
gdb, when gdb stopped I got a message 'Debugger Segmentation Fault' and gdb
prompt had stopped working. I fired it up again and it went smooth. I would
like to trace this why it happened. Can somebody guide how can I start
tracing it?
___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

gdb 7.5 manuall; command fo and demangle-style default value

[Дилян Палаузов]

Hello,

as of the texinfo documentation for gdb 7.5:

In the description of the command forward-search, node Searching Files 
is stated, that forward-search can be abbreviated as fo.  However 
typing  fo is ambiguous, as it can mean either forward-search or 
focus (at least gdb reports to).  Please update the manual, that 
forward-search cannot be shortened to fo.


The documentation for demangle-style says, that the default 
demangle-style is gnu.  However on my system it is auto.  I get this 
by starting gdb without parameters and typing show demangle-style.


In node Operating System Auxiliary Information is described the 
command info udot.  However on my linux-from-scratch system, when I 
type in gdb info udot it reports Undefined info command: udot.  This 
was reported also at 
http://forums.opensuse.org/english/other-forums/development/programming-scripting/451536-gdb-does-not-support-info-udot.html 
.


Със здраве
  Дилян
attachment: dilyan_palauzov.vcf___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: warnings with cvs texinfo version

[Patrice Dumas]

On Sat, Jun 23, 2012 at 03:49:11PM +0300, Eli Zaretskii wrote:

   That's true, but an asterisk '*' cannot be a valid label, 
  
  I can't see why.
 
 Because of * Menu.

I still don't get it.  It seems to me that

@menu
* *: mynode.
@end menu

is a perfectly valid menu entry, and same with @ref{mynode, , *}.

   and there
   should be a blank after *Note before the label.
  
  That, I could agree with.  I'll ask on the list.

This should be fixed now.

-- 
Pat

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb

Re: warnings with cvs texinfo version

[Patrice Dumas]

On Thu, Jun 21, 2012 at 05:52:55AM +0300, Eli Zaretskii wrote:
 
  ./gdb.texinfo:190: warning: @contents should only appear at beginning or 
  end of document

This warning is no longer there, it was not clearly wrong in formats
other than TeX, and we don't want to have something specific for output
formats.  This issue will be revisited later, but in the mean time
this one is no longer there...

-- 
Pat

___
bug-gdb mailing list
bug-gdb@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gdb