kdbg-l Mailing List for KDbg
Brought to you by:
j6t
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
(6) |
Nov
(5) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(2) |
Feb
(2) |
Mar
(3) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
2002 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
(3) |
May
(3) |
Jun
|
Jul
(9) |
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(2) |
Dec
(3) |
2003 |
Jan
(1) |
Feb
(8) |
Mar
(8) |
Apr
(9) |
May
(10) |
Jun
(4) |
Jul
(11) |
Aug
|
Sep
(3) |
Oct
(11) |
Nov
(7) |
Dec
|
2004 |
Jan
|
Feb
(5) |
Mar
(5) |
Apr
(2) |
May
(16) |
Jun
(4) |
Jul
|
Aug
(1) |
Sep
(4) |
Oct
(7) |
Nov
(8) |
Dec
(4) |
2005 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
(13) |
Oct
(4) |
Nov
|
Dec
(2) |
2006 |
Jan
(1) |
Feb
(9) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(6) |
Aug
(3) |
Sep
(7) |
Oct
|
Nov
|
Dec
(1) |
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(4) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
(1) |
2008 |
Jan
(2) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(1) |
Oct
|
Nov
(3) |
Dec
(7) |
2009 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
(2) |
2010 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(6) |
Dec
(8) |
2011 |
Jan
(3) |
Feb
|
Mar
(10) |
Apr
(14) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2012 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(2) |
May
|
Jun
(10) |
Jul
(2) |
Aug
(5) |
Sep
(7) |
Oct
|
Nov
(3) |
Dec
(1) |
2013 |
Jan
(5) |
Feb
|
Mar
(6) |
Apr
(14) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
|
2014 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
(3) |
Oct
(6) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Johannes S. <j6...@kd...> - 2019-08-17 09:53:08
|
Am 16.08.19 um 01:37 schrieb William Tambe: > Where can I find a list of useable %% in the Global Options Dialog. > I am attempting to get kdbg to invoke "gdb" like this: > "gdb --fullname %p" > where I am assuming that %p will be replaced by the program to debug. There is no such thing as %p in this option. Where did you get the idea from? Maybe I need to fix the documentation somewhere? > Also, is it possible to pass that option string as argument to kdbg ? ie: > kdbg --option="gdb --fullname %p" I am not aware of a possibility to set this option from the command line, sorry. > Alternatively, is it possible to get kdbg to issue the gdb command > "load" followed by the program name before starting debugging ? I am afraid, no. Why do you need that? -- Hannes |
From: William T. <tam...@gm...> - 2019-08-15 23:37:50
|
Where can I find a list of useable %% in the Global Options Dialog. I am attempting to get kdbg to invoke "gdb" like this: "gdb --fullname %p" where I am assuming that %p will be replaced by the program to debug. Also, is it possible to pass that option string as argument to kdbg ? ie: kdbg --option="gdb --fullname %p" Alternatively, is it possible to get kdbg to issue the gdb command "load" followed by the program name before starting debugging ? |
From: Johannes S. <j6...@kd...> - 2018-03-27 22:42:35
|
See https://github.com/j6t/kdbg/blob/master/kdbg/gdbdriver.cpp The list of commands is around line 100. But the parsers for the output that the commands produce are sprinkled throughout the file. Most (if not all) of the callers of parsers can be found in function KDebugger::parse() around line 1010 in https://github.com/j6t/kdbg/blob/master/kdbg/debugger.cpp. -- Hannes Am 27.03.2018 um 23:32 schrieb William Tambe: > Thank you for the response. > > The only downside I see with moving to the ML-language is that it might > no longer be possible to easily seamlessly port kdbg to a new language > using gdb aliases. > > May I get pointers to which file in kdbg sources implement the different > type of commands issued through the text interface ? > > > On Mon, Mar 26, 2018, 2:56 PM Johannes Sixt <j6...@kd... > <mailto:j6...@kd...>> wrote: > > Am 24.03.2018 um 02:43 schrieb William Tambe: > > I am working on extending gdb using aliases to support a new > language; ei: > > https://sourceware.org/gdb/onlinedocs/gdb/Aliases.html#Aliases > > > > Does kdbg operate on text output from gdb, or does it communicate > > through a binary protocol with gdb ? > > > > My hope is that kdbg operate on text output from gdb such that in > > extending gdb, I would only have to insure proper text output. > > KDbg uses the regular text-based user interface of gdb. > > I consider moving to ML-language. That would reduce some ambiguities in > certain cases (backtraces, file listings, and such), but it does not > change the quality of structure values, AFAIK. For example, what is the > following? > > s = {{ a = 1 }, b = 2} > > Is it an array or is it bogus output? Spoiler: The first element is an > anonymous struct; but it is indistinguishable from an array of structs. > > If you make a new text interface, it must avoid all ambiguities, for > example, by tagging all parts of the output. > > -- Hannes > |
From: William T. <tam...@gm...> - 2018-03-27 21:32:58
|
Thank you for the response. The only downside I see with moving to the ML-language is that it might no longer be possible to easily seamlessly port kdbg to a new language using gdb aliases. May I get pointers to which file in kdbg sources implement the different type of commands issued through the text interface ? On Mon, Mar 26, 2018, 2:56 PM Johannes Sixt <j6...@kd...> wrote: > Am 24.03.2018 um 02:43 schrieb William Tambe: > > I am working on extending gdb using aliases to support a new language; > ei: > > https://sourceware.org/gdb/onlinedocs/gdb/Aliases.html#Aliases > > > > Does kdbg operate on text output from gdb, or does it communicate > > through a binary protocol with gdb ? > > > > My hope is that kdbg operate on text output from gdb such that in > > extending gdb, I would only have to insure proper text output. > > KDbg uses the regular text-based user interface of gdb. > > I consider moving to ML-language. That would reduce some ambiguities in > certain cases (backtraces, file listings, and such), but it does not > change the quality of structure values, AFAIK. For example, what is the > following? > > s = {{ a = 1 }, b = 2} > > Is it an array or is it bogus output? Spoiler: The first element is an > anonymous struct; but it is indistinguishable from an array of structs. > > If you make a new text interface, it must avoid all ambiguities, for > example, by tagging all parts of the output. > > -- Hannes > |
From: Johannes S. <j6...@kd...> - 2018-03-26 19:56:17
|
Am 24.03.2018 um 02:43 schrieb William Tambe: > I am working on extending gdb using aliases to support a new language; ei: > https://sourceware.org/gdb/onlinedocs/gdb/Aliases.html#Aliases > > Does kdbg operate on text output from gdb, or does it communicate > through a binary protocol with gdb ? > > My hope is that kdbg operate on text output from gdb such that in > extending gdb, I would only have to insure proper text output. KDbg uses the regular text-based user interface of gdb. I consider moving to ML-language. That would reduce some ambiguities in certain cases (backtraces, file listings, and such), but it does not change the quality of structure values, AFAIK. For example, what is the following? s = {{ a = 1 }, b = 2} Is it an array or is it bogus output? Spoiler: The first element is an anonymous struct; but it is indistinguishable from an array of structs. If you make a new text interface, it must avoid all ambiguities, for example, by tagging all parts of the output. -- Hannes |
From: William T. <tam...@gm...> - 2018-03-24 01:43:30
|
I am working on extending gdb using aliases to support a new language; ei: https://sourceware.org/gdb/onlinedocs/gdb/Aliases.html#Aliases Does kdbg operate on text output from gdb, or does it communicate through a binary protocol with gdb ? My hope is that kdbg operate on text output from gdb such that in extending gdb, I would only have to insure proper text output. |
From: Johannes S. <j6...@kd...> - 2017-08-03 09:55:07
|
Am 27.07.2017 um 07:01 schrieb Stuart Longland: > Hi all, > > Silly question, is there a way to specify the debugger on the command > line? Reasoning, at present I use `ddd`, sometimes I'll be using it > with the host's `gdb`, sometimes it'll be `gdb` for an embedded target. > > `ddd` supports this, I can simplify things by sourcing a script like this: >> ddd () { >> /usr/bin/ddd --gdb --debugger /usr/bin/arm-none-eabi-gdb --eval-command="target remote localhost:3333" --eval-command="monitor reset init" "$@" >> } > > Looking at kdbg, it doesn't seem to support it. No, you can't specify the debugger on the command line, sorry. Patches welcome. -- Hannes |
From: Stuart L. <st...@lo...> - 2017-07-27 05:18:33
|
Hi all, Silly question, is there a way to specify the debugger on the command line? Reasoning, at present I use `ddd`, sometimes I'll be using it with the host's `gdb`, sometimes it'll be `gdb` for an embedded target. `ddd` supports this, I can simplify things by sourcing a script like this: > ddd () { > /usr/bin/ddd --gdb --debugger /usr/bin/arm-none-eabi-gdb --eval-command="target remote localhost:3333" --eval-command="monitor reset init" "$@" > } Looking at kdbg, it doesn't seem to support it. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere. |
From: dinor g. <di...@gm...> - 2016-05-24 19:38:23
|
Hi team, Can anyone explain how do I install kdbg on centos. A guide if you have. How do I set it up on source and target. Thank you. |
From: Johannes S. <j6...@kd...> - 2014-10-23 19:51:13
|
Am 23.10.2014 um 21:30 schrieb Filipp B.: > On 23.10.2014 23:26, Johannes Sixt wrote: >> Am 23.10.2014 um 19:35 schrieb Filipp B.: >>> On 15.10.2014 23:25, Johannes Sixt wrote: >>>> [Please Cc the list as well.] >> kd...@li... >> Did you read this? I mean it. It's impolite to drag the conversation >> away from the public without reason when it began in the public. >> >>>> GDB doesn't print all that stuff that it prints to kdbg? *That* is >>>> suspicious. Are you using the same GDB as KDbg? >>> I only have one GDB. >> >> Did you check with gdb --version? >> >>>> 3. You have custom pretty-printers in effect. KDbg can't work with those >>>> because it makes GDB output unpredictable. >>> What does that mean? Where do they come from? How do I disable or enable >>> them? >> >> Frankly, I don't know how they are installed or disabled. It's a mystery >> to me. I do know that they exist and that certain projects use them >> (like LibreOffice) and have them enabled. > > Sorry, I don't use mailing lists often enough not to get by how to > respond to them. So, do I respond to you and add Cc to the list or do I > send the response to the list without sending anything to you directly? Different lists have different conventions. There's no explicit convention on this list. Please use whathever is more convenient for you. > As for gdb --version: > > $ gdb --version > GNU gdb (Gentoo 7.8 vanilla) 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 "x86_64-pc-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://bugs.gentoo.org/>. > 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". > I haven't tested GDB 7.8, yet. Perhaps something has changed since 7.6 that makes it behave differently depending on whether it runs against a pipe vs. a terminal... -- Hannes |
From: Filipp B. <b_...@zo...> - 2014-10-23 19:32:46
|
On 23.10.2014 23:26, Johannes Sixt wrote: > Am 23.10.2014 um 19:35 schrieb Filipp B.: >> On 15.10.2014 23:25, Johannes Sixt wrote: >>> [Please Cc the list as well.] > kd...@li... > Did you read this? I mean it. It's impolite to drag the conversation > away from the public without reason when it began in the public. > >>> GDB doesn't print all that stuff that it prints to kdbg? *That* is >>> suspicious. Are you using the same GDB as KDbg? >> I only have one GDB. > > Did you check with gdb --version? > >>> 3. You have custom pretty-printers in effect. KDbg can't work with those >>> because it makes GDB output unpredictable. >> What does that mean? Where do they come from? How do I disable or enable >> them? > > Frankly, I don't know how they are installed or disabled. It's a mystery > to me. I do know that they exist and that certain projects use them > (like LibreOffice) and have them enabled. > > -- Hannes > Sorry, I don't use mailing lists often enough not to get by how to respond to them. So, do I respond to you and add Cc to the list or do I send the response to the list without sending anything to you directly? As for gdb --version: $ gdb --version GNU gdb (Gentoo 7.8 vanilla) 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 "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.gentoo.org/>. 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". -- Filipp B. |
From: Johannes S. <j6...@kd...> - 2014-10-23 19:26:29
|
Am 23.10.2014 um 19:35 schrieb Filipp B.: > On 15.10.2014 23:25, Johannes Sixt wrote: >> [Please Cc the list as well.] Did you read this? I mean it. It's impolite to drag the conversation away from the public without reason when it began in the public. >> GDB doesn't print all that stuff that it prints to kdbg? *That* is >> suspicious. Are you using the same GDB as KDbg? > I only have one GDB. Did you check with gdb --version? >> 3. You have custom pretty-printers in effect. KDbg can't work with those >> because it makes GDB output unpredictable. > What does that mean? Where do they come from? How do I disable or enable > them? Frankly, I don't know how they are installed or disabled. It's a mystery to me. I do know that they exist and that certain projects use them (like LibreOffice) and have them enabled. -- Hannes |
From: Johannes S. <j6...@kd...> - 2014-10-15 19:25:34
|
[Please Cc the list as well.] Am 15.10.2014 um 21:09 schrieb Filipp B.: > On 15.10.2014 22:29, Johannes Sixt wrote: >> Am 15.10.2014 um 17:25 schrieb Filipp B.: >>> Hello. I am trying to debug Clementine audio player with kdbg and I have >>> a problem - if I run it normally or with gdb or cgdb, everything's ok >>> and the program works, however if I use kdbg to run it, it seems to get >>> stuck at updating library while writing much more additional debug info >>> to kdbg's terminal like these 5 lines: >>> >>> 19:05:28.762 DEBUG MessageReply<MessageType>:90 Releasing ID 3621 >>> (finished) >>> 19:05:28.763 DEBUG _MessageReplyBase:26 Acquired ID 3621 >>> 19:05:28.763 DEBUG _MessageReplyBase:24 Waiting on ID 3622 >>> 19:05:28.764 DEBUG TagReader:119 Reading tags from >>> "/home/crabman/sync/music//l'arcenciel" >>> 19:05:28.764 INFO TagReader:129 TagLib hasn't been >>> able to read "/home/crabman/sync/music//l'arcenciel" file >>> >>> I have no idea what is the reason of this and why it doesn't happen with >>> just gdb. Does kdbg do something strange to the programs user runs in it? >>> >> >> Not that I know of. You can capture the conversation between KDbg and >> gdb like this: >> >> kdbg -t /tmp/gdb-transcript thatprogram >> >> Inspect that file to get a feeling how KDbg talks to gdb. If you find >> something suspicous, send the transcript to me. > > The suspicious thing is there is nothing suspicious in the transcript. I > tried manually executing gdb with the command set in kdbg's settings > (gdb --fullname --nx) and setting all the options kdbg sets (except for > tty /dev/pts/<number>) but when I do that, it still doesn't get stuck > and doesn't print all that stuff that it prints to kdbg, so I have only > 2 guesses: GDB doesn't print all that stuff that it prints to kdbg? *That* is suspicious. Are you using the same GDB as KDbg? > 1. kdbg writes something to that /dev/pts/<number> terminal which makes > clementine behave the way it does This certainly does not happen. > 2. Qt used in clementine somehow detects different types of output > terminals depending on whether its output is redirected to > pseudoterminal or not and modifies the program's behaviour depending on > that (I'll have to figure out how to create my own pts device to check > whether this is true). > > If neither of these guesses is the case, then I don't know what to think. 3. You have custom pretty-printers in effect. KDbg can't work with those because it makes GDB output unpredictable. -- Hannes |
From: Johannes S. <j6...@kd...> - 2014-10-15 18:30:15
|
Am 15.10.2014 um 17:25 schrieb Filipp B.: > Hello. I am trying to debug Clementine audio player with kdbg and I have > a problem - if I run it normally or with gdb or cgdb, everything's ok > and the program works, however if I use kdbg to run it, it seems to get > stuck at updating library while writing much more additional debug info > to kdbg's terminal like these 5 lines: > > 19:05:28.762 DEBUG MessageReply<MessageType>:90 Releasing ID 3621 > (finished) > 19:05:28.763 DEBUG _MessageReplyBase:26 Acquired ID 3621 > 19:05:28.763 DEBUG _MessageReplyBase:24 Waiting on ID 3622 > 19:05:28.764 DEBUG TagReader:119 Reading tags from > "/home/crabman/sync/music//l'arcenciel" > 19:05:28.764 INFO TagReader:129 TagLib hasn't been > able to read "/home/crabman/sync/music//l'arcenciel" file > > I have no idea what is the reason of this and why it doesn't happen with > just gdb. Does kdbg do something strange to the programs user runs in it? > Not that I know of. You can capture the conversation between KDbg and gdb like this: kdbg -t /tmp/gdb-transcript thatprogram Inspect that file to get a feeling how KDbg talks to gdb. If you find something suspicous, send the transcript to me. -- Hannes |
From: Filipp B. <b_...@zo...> - 2014-10-15 15:27:18
|
Hello. I am trying to debug Clementine audio player with kdbg and I have a problem - if I run it normally or with gdb or cgdb, everything's ok and the program works, however if I use kdbg to run it, it seems to get stuck at updating library while writing much more additional debug info to kdbg's terminal like these 5 lines: 19:05:28.762 DEBUG MessageReply<MessageType>:90 Releasing ID 3621 (finished) 19:05:28.763 DEBUG _MessageReplyBase:26 Acquired ID 3621 19:05:28.763 DEBUG _MessageReplyBase:24 Waiting on ID 3622 19:05:28.764 DEBUG TagReader:119 Reading tags from "/home/crabman/sync/music//l'arcenciel" 19:05:28.764 INFO TagReader:129 TagLib hasn't been able to read "/home/crabman/sync/music//l'arcenciel" file I have no idea what is the reason of this and why it doesn't happen with just gdb. Does kdbg do something strange to the programs user runs in it? -- Filipp B. |
From: John L. <joh...@gm...> - 2014-09-13 10:32:44
|
On 13 September 2014 19:21, Johannes Sixt <j6...@kd...> wrote: >> Or know how to change the colours that kdbg uses? Particularly, the >> current line highlight? > You can't. Highlight colors are hard-coded. There seemed to be some relationship with the KDE colour scheme... which was partially updated when I changed the scheme. I see now that my main problem was that partial update, that if I'd restarted kdbg after changing scheme, more sanity would have prevailed. I'll poke around in the source. Thanks for a great tool. |
From: Johannes S. <j6...@kd...> - 2014-09-13 07:52:17
|
Am 13.09.2014 um 06:02 schrieb John Little: > I had call to fire up kdbg recently, to diagnose a problem in some C. > > The code window was unreadable, most of the code was dark grey on > darker grey. I was using the Obsidian Coast colour Scheme, so I > changed to Default, and got light grey on slightly lighter grey. I > blundered around changing colours in system settings till I could get > the job done, though the highlight of the current line became bright > white, washing out any text on that line. > > Does anyone have a KDE colour scheme, preferably dark, that works well > with kdbg? > > Or know how to change the colours that kdbg uses? Particularly, the > current line highlight? You can't. Highlight colors are hard-coded. The highlight color of the current line is a bright gray, so any light text color won't work well. > Ideally, kdbg would use some kind of kate part, because the syntax > colouring there is well defined, though I don't use kate myself. That would be preferable, of course. -- Hannes |
From: John L. <joh...@gm...> - 2014-09-13 04:02:48
|
I had call to fire up kdbg recently, to diagnose a problem in some C. The code window was unreadable, most of the code was dark grey on darker grey. I was using the Obsidian Coast colour Scheme, so I changed to Default, and got light grey on slightly lighter grey. I blundered around changing colours in system settings till I could get the job done, though the highlight of the current line became bright white, washing out any text on that line. Does anyone have a KDE colour scheme, preferably dark, that works well with kdbg? Or know how to change the colours that kdbg uses? Particularly, the current line highlight? Ideally, kdbg would use some kind of kate part, because the syntax colouring there is well defined, though I don't use kate myself. Thanks for any attention, John Little |
From: Alessandro P. <pag...@za...> - 2014-07-23 07:08:37
|
Thank you Hannes for your prompt reply. 2014-07-22 18:33 GMT+02:00 Johannes Sixt <j6...@kd...>: > Am 22.07.2014 15:47, schrieb Alessandro Paganelli: > > Hi all, > > > > I'm trying to remotely debug a firmware we've developed for a STM32F4 > > board, using kdbg, following the procedure from: > > > > http://fun-tech.se/stm32/OpenOCD/gdb.php > > > > Our setup is based on: > > > > - Ubuntu 13.10 x86_64 bit > > - kdbg 2.5.2 and kdbg 2.5.3 > > - gcc-arm-none-eabi-4_7-2013q2 arm toolchain > > - openocd 0.7.0 > > > > When we try to start kdbg with: > > > > kdbg -r localhost:3333 main.elf > > > > we get the following error: > > > > GDB exited unexpectedly. > > Restart the session (e.g. with File|Executable). > > > > However, when trying to use command line & plain gdb, everything works > fine. > > Since this issue came out just a couple of days ago (i.e., we used kdbg > > a lot before this issue and everythin was fine), we suspect that some > > configuration file is broken. > > However, reinstalling or purging kdbg package didn't help ... > > Make a trace file > > kdbg -t /tmp/gdb-transcript -r localhost:3333 main.elf > > and inspect it. Maybe you get a clue what's wrong. An interesting > experiment would be to repeat the commands you see in the trace file on > the command line; do you also observe a crash? > > By using the trace file we found the source of this issue: (kdbg)print ( data.intensity - floor( data.intensity ) ) * 10 /home/build/work/GCC-4-7-build/src/gdb/gdb/regcache.c:886: internal-error: regcache_cooked_write: Assertion `regnum >= 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. That was a watchpoint we used a couple of days ago, which, however, did not disappear on kdbg close / reinstall / purge / whatever. > Any ideas? > > How could I copletely reset our kdbg setup (removing all configs, all > > watches, etc)? > > No idea. > > -- Hannes > > After some grep & find, we have found several session files inside ~/.kde/share/apps/kdbg/session Last one contained the previous erroneous watchpoint. By removing that line, kdbg started working perfectly :-) Thank you for your help! Regards, Alessandro -- *Via Marche 10, Sassuolo 41049 (MO)* Tel (+39) 0536 999711 Fax (+39) 0536 999765 www.zanasi.it - www.zanasi-coding.com INFORMATIVA SULLA PRIVACY Ai sensi del D.Lgs. n.196 del 30.6.2003, si precisa che le informazioni contenute in questo messaggio e nei suoi eventuali allegati sono riservate e per uso esclusivo del destinatario. Nessuno, all'infuori dello stesso, puo' copiare o distribuire il messaggio, o parte di esso, a terzi. Chiunque riceva questo messaggio per errore, e' pregato di distruggerlo e di informare il mittente. PRIVACY NOTICE According to the D.Lgs. n. 196, dated 30.6.2003, this document and its attachments are confidential and intended for the named addressee(s) only. If you are not the intended recipient of this message, any use or dissemination of this email is prohibited. If you have received this document by mistake, please notify the sender and destroy immediately all physical and/or electronic copies. |
From: Johannes S. <j6...@kd...> - 2014-07-22 17:01:00
|
Am 22.07.2014 15:47, schrieb Alessandro Paganelli: > Hi all, > > I'm trying to remotely debug a firmware we've developed for a STM32F4 > board, using kdbg, following the procedure from: > > http://fun-tech.se/stm32/OpenOCD/gdb.php > > Our setup is based on: > > - Ubuntu 13.10 x86_64 bit > - kdbg 2.5.2 and kdbg 2.5.3 > - gcc-arm-none-eabi-4_7-2013q2 arm toolchain > - openocd 0.7.0 > > When we try to start kdbg with: > > kdbg -r localhost:3333 main.elf > > we get the following error: > > GDB exited unexpectedly. > Restart the session (e.g. with File|Executable). > > However, when trying to use command line & plain gdb, everything works fine. > Since this issue came out just a couple of days ago (i.e., we used kdbg > a lot before this issue and everythin was fine), we suspect that some > configuration file is broken. > However, reinstalling or purging kdbg package didn't help ... Make a trace file kdbg -t /tmp/gdb-transcript -r localhost:3333 main.elf and inspect it. Maybe you get a clue what's wrong. An interesting experiment would be to repeat the commands you see in the trace file on the command line; do you also observe a crash? > Any ideas? > How could I copletely reset our kdbg setup (removing all configs, all > watches, etc)? No idea. -- Hannes |
From: Alessandro P. <pag...@za...> - 2014-07-22 14:12:49
|
Hi all, I'm trying to remotely debug a firmware we've developed for a STM32F4 board, using kdbg, following the procedure from: http://fun-tech.se/stm32/OpenOCD/gdb.php Our setup is based on: - Ubuntu 13.10 x86_64 bit - kdbg 2.5.2 and kdbg 2.5.3 - gcc-arm-none-eabi-4_7-2013q2 arm toolchain - openocd 0.7.0 When we try to start kdbg with: kdbg -r localhost:3333 main.elf we get the following error: GDB exited unexpectedly. Restart the session (e.g. with File|Executable). However, when trying to use command line & plain gdb, everything works fine. Since this issue came out just a couple of days ago (i.e., we used kdbg a lot before this issue and everythin was fine), we suspect that some configuration file is broken. However, reinstalling or purging kdbg package didn't help ... Any ideas? How could I copletely reset our kdbg setup (removing all configs, all watches, etc)? Thank you in advance, Alessandro *Alessandro Paganelli, PhD *Technical Dept. pag...@za... -- *Via Marche 10, Sassuolo 41049 (MO)* Tel (+39) 0536 999711 Fax (+39) 0536 999765 www.zanasi.it - www.zanasi-coding.com INFORMATIVA SULLA PRIVACY Ai sensi del D.Lgs. n.196 del 30.6.2003, si precisa che le informazioni contenute in questo messaggio e nei suoi eventuali allegati sono riservate e per uso esclusivo del destinatario. Nessuno, all'infuori dello stesso, puo' copiare o distribuire il messaggio, o parte di esso, a terzi. Chiunque riceva questo messaggio per errore, e' pregato di distruggerlo e di informare il mittente. PRIVACY NOTICE According to the D.Lgs. n. 196, dated 30.6.2003, this document and its attachments are confidential and intended for the named addressee(s) only. If you are not the intended recipient of this message, any use or dissemination of this email is prohibited. If you have received this document by mistake, please notify the sender and destroy immediately all physical and/or electronic copies. |
From: Jonathan D. <jon...@gm...> - 2014-07-17 18:48:03
|
On Wed, Jul 16, 2014 at 1:41 AM, <ma...@ci...> wrote: > Hi, > Thanks for answer. > Sadly i am in china and formums solutions pages is limited, > like google. The fisrt ussue problem (see above) before i commented i.e, > > " >> 1) Sorry-Kdbg. Gdb: Reding symbol from /my directories" > > is a mistakes i have when try to loading my executable files. > I dont know if i need some particular library. I attached the screen > mistakes. > After that, the execution menu is not able...a dont know why. > If you have some issues to reolve this problem is welcome. > > Thanks. > > Nelson Unfortunately, I don't have any advice on the first problem. But if the "MNG error 11" is preventing kdbg from running, you should delete or rename /usr/share/kde4/apps/kdbg/icons/hicolor/22x22/actions/pulse.mng. |
From: Jonathan D. <jon...@gm...> - 2014-07-16 04:03:06
|
On Tue, Jul 15, 2014 at 1:32 AM, <ma...@ci...> wrote: > Hi Members, > My Name is Nelson Lafontaine and i use kdbg for debugging my > applications. > However, when trying to use kdbg in ubuntu 13. and 14.04, however, two > types > of mistakes i have: > > 1) Sorry-Kdbg. Gdb: Reding symbol from /my directories > > 2) MNG error 11: Function is invalid at this point; chunk MHDR; subcode > 0:0 > in ubuntu 14.04 > > The first one, the run command is not activated once i load the > execultable file. > > The second one not source well the kdbg program showing the above line. Not sure if I understand your problems completely, but #2 has been known for a while. See https://bugs.launchpad.net/ubuntu/+source/kdbg/+bug/1311893. You can delete/move the icon file as described in that bug report for a temporary fix. - Jon Doman |
From: <ma...@ci...> - 2014-07-15 06:32:23
|
Hi Members, My Name is Nelson Lafontaine and i use kdbg for debugging my applications. However, when trying to use kdbg in ubuntu 13. and 14.04, however, two types of mistakes i have: 1) Sorry-Kdbg. Gdb: Reding symbol from /my directories 2) MNG error 11: Function is invalid at this point; chunk MHDR; subcode 0:0 in ubuntu 14.04 The first one, the run command is not activated once i load the execultable file. The second one not source well the kdbg program showing the above line. There are solution for this. Any ideas is welcome. Regards Nelson |
From: <ma...@ci...> - 2014-07-14 09:44:46
|
Hi Members, My Name is Nelson Lafontaine and i use kdbg for debugging my applications. However, when trying to use kdbg in ubuntu 13. and 14.04, however, two types of mistakes i have: 1) Sorry-Kdbg. Gdb: Reding symbol from /my directories 2) MNG error 11: Function is invalid at this point; chunk MHDR; subcode 0:0 in ubuntu 14.04 The first one, the run command is not activated once i load the execultable file. The second one not source well the kdbg program showing the above line. There are solution for this. Any ideas is welcome. Regards Nelson |