Re: Help installing gdb package using apt
Hello everyone, Thank you so much for your assistance on this matter. The solution was found. Updating the sources list to include: deb http://deb.debian.org/debian/ bookworm main non-free-firmware deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware deb http://security.debian.org/debian-security bookworm-security main non-free-firmware deb-src http://security.debian.org/debian-security bookworm-security main non-free-firmware # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports deb http://deb.debian.org/debian/ bookworm-updates main non-free-firmware deb-src http://deb.debian.org/debian/ bookworm-updates main non-free-firmware seems to have fixed my issue. I believe this is entirely a problem of my own causing. My initial plan for this system was to keep it offline. I later decided to take it online. I updated the sources list with a single source, thinking that one would be necessary to get connected, and it worked... for a while. Thanks again for all the help! Demetrius Stanton On Mon, Jul 15, 2024 at 5:59 PM Tom Dial wrote: > Hi Demetrius. > > See the embedded observations below. > > > > On 7/15/24 05:42, Demetrius Stanton wrote: > > Hi! > > > > My name is Demetrius Stanton. It was suggested that I reach out for a > problem I'm experiencing trying to install gdb on my system. I'm willing to > submit whatever information is necessary to try and get this issue resolved. > > > > I recently encountered a weird error, and I can't seem to find a fix > online. When I run the command ` sudo apt update && sudo apt install gdb -y > `, I receive an 404 error stating failed to fetch > https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u > <https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u>*4*_amd64.deb. > When I navigate to the https://deb.debian.org/debian/pool/main/g/glibc/ < > https://deb.debian.org/debian/pool/main/g/glibc/> site, I'm able to find > libc6-dbg_2.36-9+deb12u*7*_amd64.deb. Though I'm reasonably confident I > could use wget to download and then dpkg to install this file, I am > concerned I could adversely affect the stability of my system. I'm sure it > would be safer for me to use apt to manage my packages. > > > > How do I proceed forward from here? > > > > I posed this question to debian-rele...@lists.debian.org>> and received the following in response: > > > > " > > Welcome to Debian. > > > > You might be able to resolve this issue you have by running > > > > sudo apt update > > > > followed by > > > > sudo apt full-upgrade > > > > and resolve resulting errors, if any occur, and then try reinstalling > gdb. The particular error - attempting to fetch and install what looks like > an out of date version of libc6-dbg_2.36-9 - suggests your system might not > be fully up to date. If that helps, good; otherwise: > > > > You would do better to ask this question on the debian-user list ( > debian-user@lists.debian.org <mailto:debian-user@lists.debian.org>). It > is a fairly active list that includes people with a wide range of knowledge > and who generally are willing to help. > > > > You should provide additional information (and will be asked to do so if > you do not), since what you give above is a bit sketchy. In particular, I > suggest you include in the question a copy of your /etc/apt/sources.list > and any files that are in the directory /etc/apt/sources.list.d. It might > also be useful to include a copy of your /etc/debian_version and > /etc/os-release files, which will establish the exact update level of your > system. > > > > In general, it is probably a bad idea to poke around in /debian/pool/ in > the distribution repository for things to install. Those directories > contain software for several releases and mixing versions from different > releases may, as you suspect, result in an unstable system. Using apt is > much safer, but depends on correct setup of the files in the /etc/apt/ > directory that describe the range of software installed. > > > > Regards, > > > > " > > Attempting the prescribed fix yielded the following: > > > > $ sudo apt update && sudo apt full-upgrade > > [sudo] password for demetrius: > > Hit:1 https://dl.google.com/linux/chrome/deb < > https://dl.google.com/linux/chrome/deb> stable InRelease > > Hit:2 https://deb.debian.org/debian <https://deb.debian.org/debian> > bookworm InRelease > > Hit:3 https://packages.microsoft.com/repos/code < &
Re: Help installing gdb package using apt
Hi Demetrius. See the embedded observations below. On 7/15/24 05:42, Demetrius Stanton wrote: Hi! My name is Demetrius Stanton. It was suggested that I reach out for a problem I'm experiencing trying to install gdb on my system. I'm willing to submit whatever information is necessary to try and get this issue resolved. I recently encountered a weird error, and I can't seem to find a fix online. When I run the command ` sudo apt update && sudo apt install gdb -y `, I receive an 404 error stating failed to fetch https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u <https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u>*4*_amd64.deb. When I navigate to the https://deb.debian.org/debian/pool/main/g/glibc/ <https://deb.debian.org/debian/pool/main/g/glibc/> site, I'm able to find libc6-dbg_2.36-9+deb12u*7*_amd64.deb. Though I'm reasonably confident I could use wget to download and then dpkg to install this file, I am concerned I could adversely affect the stability of my system. I'm sure it would be safer for me to use apt to manage my packages. How do I proceed forward from here? I posed this question to mailto:debian-rele...@lists.debian.org>> and received the following in response: " Welcome to Debian. You might be able to resolve this issue you have by running sudo apt update followed by sudo apt full-upgrade and resolve resulting errors, if any occur, and then try reinstalling gdb. The particular error - attempting to fetch and install what looks like an out of date version of libc6-dbg_2.36-9 - suggests your system might not be fully up to date. If that helps, good; otherwise: You would do better to ask this question on the debian-user list (debian-user@lists.debian.org <mailto:debian-user@lists.debian.org>). It is a fairly active list that includes people with a wide range of knowledge and who generally are willing to help. You should provide additional information (and will be asked to do so if you do not), since what you give above is a bit sketchy. In particular, I suggest you include in the question a copy of your /etc/apt/sources.list and any files that are in the directory /etc/apt/sources.list.d. It might also be useful to include a copy of your /etc/debian_version and /etc/os-release files, which will establish the exact update level of your system. In general, it is probably a bad idea to poke around in /debian/pool/ in the distribution repository for things to install. Those directories contain software for several releases and mixing versions from different releases may, as you suspect, result in an unstable system. Using apt is much safer, but depends on correct setup of the files in the /etc/apt/ directory that describe the range of software installed. Regards, " Attempting the prescribed fix yielded the following: $ sudo apt update && sudo apt full-upgrade [sudo] password for demetrius: Hit:1 https://dl.google.com/linux/chrome/deb <https://dl.google.com/linux/chrome/deb> stable InRelease Hit:2 https://deb.debian.org/debian <https://deb.debian.org/debian> bookworm InRelease Hit:3 https://packages.microsoft.com/repos/code <https://packages.microsoft.com/repos/code> stable InRelease Hit:4 https://brave-browser-apt-release.s3.brave.com <https://brave-browser-apt-release.s3.brave.com> stable InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. N: Repository 'Debian bookworm' changed its 'firmware component' value from 'non-free' to 'non-free-firmware' N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split <https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split> Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt install gdb -y Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libbabeltrace1 libboost-regex1.74.0 libc6-dbg libdebuginfod-common libdebuginfod1 libipt2 libsource-highlight-common libsource-highlight4v5 Suggested packages: gdb-doc gdbserver The following NEW packages will be installed: gdb libbabeltrace1 libboost-regex1.74.0 libc6-dbg libdebuginfod-common libdebuginfod1 libipt2 libsource-highlight-common libsource-highlight4v5 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 7,458 kB/12.5 MB of archives. After this operation, 28.4 MB of additional disk space will be used. Err:1 https://deb.debian.org/debian <ht
Re: Help installing gdb package using apt
On Mon, Jul 15, 2024 at 11:07 AM Demetrius Stanton wrote: > > Hi! > > My name is Demetrius Stanton. It was suggested that I reach out for a problem > I'm experiencing trying to install gdb on my system. I'm willing to submit > whatever information is necessary to try and get this issue resolved. > > I recently encountered a weird error, and I can't seem to find a fix online. > When I run the command ` sudo apt update && sudo apt install gdb -y `, I > receive an 404 error stating failed to fetch > https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u4_amd64.deb. > When I navigate to the https://deb.debian.org/debian/pool/main/g/glibc/ > site, I'm able to find libc6-dbg_2.36-9+deb12u7_amd64.deb. Though I'm > reasonably confident I could use wget to download and then dpkg to install > this file, I am concerned I could adversely affect the stability of my > system. I'm sure it would be safer for me to use apt to manage my packages. > > How do I proceed forward from here? > > I posed this question to and received the > following in response: > > " > Welcome to Debian. > > You might be able to resolve this issue you have by running > >sudo apt update > > followed by > >sudo apt full-upgrade > > and resolve resulting errors, if any occur, and then try reinstalling gdb. > The particular error - attempting to fetch and install what looks like an out > of date version of libc6-dbg_2.36-9 - suggests your system might not be fully > up to date. If that helps, good; otherwise: <.. snip ..> > Attempting the prescribed fix yielded the following: > > $ sudo apt update && sudo apt full-upgrade > [sudo] password for demetrius: > Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease > Hit:2 https://deb.debian.org/debian bookworm InRelease > Hit:3 https://packages.microsoft.com/repos/code stable InRelease > Hit:4 https://brave-browser-apt-release.s3.brave.com stable InRelease You're missing bookworm-security and bookworm-updates from your sources list. Try it again with them in your /etc/apt/sources.list lee@laptop:~$ cat /etc/apt/sources.list #deb cdrom:[Debian GNU/Linux 12.5.0 _Bookworm_ - Official amd64 NETINST with firmware 20240210-11:27]/ bookworm contrib main non-free-firmware deb http://deb.debian.org/debian/ bookworm main non-free-firmware deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware deb http://security.debian.org/debian-security bookworm-security main non-free-firmware deb-src http://security.debian.org/debian-security bookworm-security main non-free-firmware # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports deb http://deb.debian.org/debian/ bookworm-updates main non-free-firmware deb-src http://deb.debian.org/debian/ bookworm-updates main non-free-firmware Regards, Lee
Re: Help installing gdb package using apt
Hi Demetrius, On 15/07/24 17:12, Demetrius Stanton wrote: [...] I recently encountered a weird error, and I can't seem to find a fix online. When I run the command ` sudo apt update && sudo apt install gdb -y `, I receive an 404 error stating failed to fetch https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u*4*_amd64.deb. When I navigate to the https://deb.debian.org/debian/pool/main/g/glibc/ site, I'm able to find libc6-dbg_2.36-9+deb12u*7*_amd64.deb. Though I'm reasonably confident I could use wget to download and then dpkg to install this file, I am concerned I could adversely affect the stability of my system. I'm sure it would be safer for me to use apt to manage my packages. A quick fix might be to use a different Debian mirror: https://www.debian.org/mirror/list This is a bad solution, however, even if it works. I am curious what it is and am looking forward to the big people to diagnose and solve it. Regards, Pranjal
Re: Help installing gdb package using apt
On 2024-07-15 at 07:42, Demetrius Stanton wrote: > Hi! > > My name is Demetrius Stanton. It was suggested that I reach out for a > problem I'm experiencing trying to install gdb on my system. I'm willing to > submit whatever information is necessary to try and get this issue > resolved. > > I recently encountered a weird error, and I can't seem to find a fix > online. When I run the command ` sudo apt update && sudo apt install gdb -y > `, I receive an 404 error stating failed to fetch > https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u*4*_amd64.deb. > How do I proceed forward from here? > > I posed this question to and received the > following in response: > The particular error - attempting to fetch and install what looks like an > out of date version of libc6-dbg_2.36-9 - suggests your system might not be > fully up to date. > You should provide additional information (and will be asked to do so if > you do not), since what you give above is a bit sketchy. In particular, I > suggest you include in the question a copy of your /etc/apt/sources.list > and any files that are in the directory /etc/apt/sources.list.d. > Attempting the prescribed fix yielded the following: > > $ sudo apt update && sudo apt full-upgrade > [sudo] password for demetrius: > Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease > Hit:2 https://deb.debian.org/debian bookworm InRelease > Hit:3 https://packages.microsoft.com/repos/code stable InRelease > Hit:4 https://brave-browser-apt-release.s3.brave.com stable InRelease > Err:1 https://deb.debian.org/debian bookworm/main amd64 libc6-dbg amd64 > 2.36-9+deb12u4 > 404 Not Found [IP: 2a04:4e42:d::644 443] > E: Failed to fetch > https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u4_amd64.deb > 404 Not Found [IP: 2a04:4e42:d::644 443] > E: Unable to fetch some archives, maybe run apt-get update or try with > --fix-missing? > > So now I'm reaching out. > Here's the info that was recommended I add: > > $ cat /etc/apt/sources.list > # deb cdrom:[Debian GNU/Linux 12.2.0 _Bookworm_ - Official amd64 DVD > Binary-1 with firmware 20231007-10:29]/ bookworm main non-free-firmware > deb https://deb.debian.org/debian/ bookworm main contrib > $ ls /etc/apt/sources.list.d/ > brave-browser-release.list google-chrome.list vscode.list > $ cat /etc/apt/sources.list.d/brave-browser-release.list > deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] > https://brave-browser-apt-release.s3.brave.com/ stable main > $ cat /etc/apt/sources.list.d/google-chrome.list > ### THIS FILE IS AUTOMATICALLY CONFIGURED ### > # You may comment out this entry, but any other modifications may be lost. > deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main > $ cat /etc/apt/sources.list.d/vscode.list > ### THIS FILE IS AUTOMATICALLY CONFIGURED ### > # You may comment out this entry, but any other modifications may be lost. > deb [arch=amd64,arm64,armhf] https://packages.microsoft.com/repos/code > stable main This sources.list file is missing entries for the portions of the archive that contain the debug-symbols packages. For comparison, here is a trio of successive lines from my own sources.list: >> deb http://ftp.us.debian.org/debian/ testing main non-free non-free-firmware >> contrib >> deb-src http://ftp.us.debian.org/debian/ testing main non-free >> non-free-firmware contrib >> deb http://debug.mirrors.debian.org/debian-debug/ testing-debug main >> non-free non-free-firmware contrib These specify where APT should look for A: the binary packages, B: the source packages, and D: the debug-symbols packages, for Debian testing. (I configure sources list with the names 'stable', 'testing', and 'sid', rather than using the release codenames; I do this on purpose, but it is typically recommended to use the release codenames, and you are probably correct for your situation that you use them.) Try adding deb https://debug.mirrors.debian.org/debian-debug/ bookworm-debug main contrib (and/or similar for any other official Debian repositories you want to get debug packages from), and repeating the suggested 'apt update' command, then installing the desired package(s) again. I don't think a full-upgrade will be necessary in your circumstances, although it would *probably* not hurt. If the install attempt still fails, you can try 'apt full-upgrade' and see whether it produces something reasonable. > If there's anything you can suggest to help, it would be greatly > appreciated! I hope that is enough to lead you somewhere useful! -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Help installing gdb package using apt
Hi! My name is Demetrius Stanton. It was suggested that I reach out for a problem I'm experiencing trying to install gdb on my system. I'm willing to submit whatever information is necessary to try and get this issue resolved. I recently encountered a weird error, and I can't seem to find a fix online. When I run the command ` sudo apt update && sudo apt install gdb -y `, I receive an 404 error stating failed to fetch https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u*4*_amd64.deb. When I navigate to the https://deb.debian.org/debian/pool/main/g/glibc/ site, I'm able to find libc6-dbg_2.36-9+deb12u*7*_amd64.deb. Though I'm reasonably confident I could use wget to download and then dpkg to install this file, I am concerned I could adversely affect the stability of my system. I'm sure it would be safer for me to use apt to manage my packages. How do I proceed forward from here? I posed this question to and received the following in response: " Welcome to Debian. You might be able to resolve this issue you have by running sudo apt update followed by sudo apt full-upgrade and resolve resulting errors, if any occur, and then try reinstalling gdb. The particular error - attempting to fetch and install what looks like an out of date version of libc6-dbg_2.36-9 - suggests your system might not be fully up to date. If that helps, good; otherwise: You would do better to ask this question on the debian-user list ( debian-user@lists.debian.org). It is a fairly active list that includes people with a wide range of knowledge and who generally are willing to help. You should provide additional information (and will be asked to do so if you do not), since what you give above is a bit sketchy. In particular, I suggest you include in the question a copy of your /etc/apt/sources.list and any files that are in the directory /etc/apt/sources.list.d. It might also be useful to include a copy of your /etc/debian_version and /etc/os-release files, which will establish the exact update level of your system. In general, it is probably a bad idea to poke around in /debian/pool/ in the distribution repository for things to install. Those directories contain software for several releases and mixing versions from different releases may, as you suspect, result in an unstable system. Using apt is much safer, but depends on correct setup of the files in the /etc/apt/ directory that describe the range of software installed. Regards, " Attempting the prescribed fix yielded the following: $ sudo apt update && sudo apt full-upgrade [sudo] password for demetrius: Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease Hit:2 https://deb.debian.org/debian bookworm InRelease Hit:3 https://packages.microsoft.com/repos/code stable InRelease Hit:4 https://brave-browser-apt-release.s3.brave.com stable InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. N: Repository 'Debian bookworm' changed its 'firmware component' value from 'non-free' to 'non-free-firmware' N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt install gdb -y Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libbabeltrace1 libboost-regex1.74.0 libc6-dbg libdebuginfod-common libdebuginfod1 libipt2 libsource-highlight-common libsource-highlight4v5 Suggested packages: gdb-doc gdbserver The following NEW packages will be installed: gdb libbabeltrace1 libboost-regex1.74.0 libc6-dbg libdebuginfod-common libdebuginfod1 libipt2 libsource-highlight-common libsource-highlight4v5 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 7,458 kB/12.5 MB of archives. After this operation, 28.4 MB of additional disk space will be used. Err:1 https://deb.debian.org/debian bookworm/main amd64 libc6-dbg amd64 2.36-9+deb12u4 404 Not Found [IP: 2a04:4e42:d::644 443] E: Failed to fetch https://deb.debian.org/debian/pool/main/g/glibc/libc6-dbg_2.36-9%2bdeb12u4_amd64.deb 404 Not Found [IP: 2a04:4e42:d::644 443] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? So now I'm reaching out. Here's the info that was recommended I add: $ cat /etc/apt/sources.list # deb cdrom:[Debian GNU/Linux 12.2.0 _Bookworm_ - Official amd64 DVD Binary-1 with firmware 20231007-10:29]/ bookworm main non-free-firmware deb https://deb.debian.org/debian/ bookworm main contrib $ ls /etc/apt/sources.list.
Re: removing gdb-minimal removed plasma-desktop?
On Sun 14 Jan 2024 at 08:54:35 (+0100), Morten Hauke Solvang wrote: > Short version: "apt remove gdb-minimal" seems to have also removed > plasma-desktop + a bunch of related packages. > > Curious if there are any good debugging tips for figuring out what > happened here. > Or maybe I'm missing something obvious about how apt works, and this > is expected behavior? > > Yesterday, I was trying to use gdb, and realized I had gdb-minimal > installed instead of the regular gdb package. > > To fix this, I first ran "apt remove gdb-minimal". > My assumption was that I then would have to run "apt install gdb". > But turns out that invoking "gdb" after running "apt remove > gdb-minimal", I had the full version of gdb installed. > I didn't think more about it, went on using gdb and later shut down > the computer. I'd be interested to know what happens if you (had) run: apt install gdb+ gdb-minimal- (As I don't install DEs, I don't tend to get these complex dependency problems.) $ man apt [ … ] install, reinstall, remove, purge (apt-get(8)) Performs the requested action on one or more packages specified via regex(7), glob(7) or exact match. The requested action can be overridden for specific packages by appending a plus (+) to the package name to install this package or a minus (-) to remove it. [ … ] Cheers, David.
Re: Re: removing gdb-minimal removed plasma-desktop?
On 2024-01-14 08:54 +0100, Morten Hauke Solvang wrote: > That assumption was a bit misguided. The correct way would have been to > "apt install gdb" _without_ first removing gdb-minimal, that would have > avoided the removal of reverse dependencies. > Pretty sure not only was this information printed, apt also asks for > confirmation if it has to install or remove more packages than > requested. But it did what you told it to do, although the outcome > might not have been what you desired. Right, makes sense to me. I was apparently just asleep at the wheel. > Good you sorted it out. The only question is why apt installed gdb even > though it removed plasma-workspace anyway. When I tried to replicate > your situation in a bookworm chroot, "apt remove gdb-minimal" removes > plasma-workspace but does not install gdb. I just ran 'apt install gdb-minimal' to get back to the state from before yesterday. If I then run 'apt remove gdb-minimal' I do infact see the warning you were saying I would see. $ sudo apt remove gdb-minimal ... (trimmed output) The following additional packages will be installed: gdb Suggested packages: gdb-doc gdbserver The following packages will be REMOVED: gdb-minimal kde-plasma-desktop kinfocenter plasma-desktop plasma-widgets-addons plasma-workspace plasma-workspace-wayland sddm-theme-breeze sddm-theme-debian-breeze The following NEW packages will be installed: gdb 0 upgraded, 1 newly installed, 9 to remove and 0 not upgraded. If I follow what you are saying, then this is all is fine, except that - It's a bit odd that plasma-desktop depends on gdb-minimal | gdb - Why is it installing gdb? - If it is installing gdb, then it shouldn't actually need to remove plasma-desktop. If I type 'n' to abort the 'apt remove ...' call, and instead install 'gdb', I see this: $ sudo apt install gdb ... (trimmed output) The following packages will be REMOVED: gdb-minimal The following NEW packages will be installed: gdb 0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Need to get 3,962 kB of archives. After this operation, 1,757 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://deb.debian.org/debian bookworm/main amd64 gdb amd64 13.1-3 [3,962 kB] Fetched 3,962 kB in 0s (34.7 MB/s) dpkg: gdb-minimal: dependency problems, but removing anyway as you requested: plasma-workspace depends on gdb-minimal | gdb; however: Package gdb-minimal is to be removed. Package gdb is not installed. Package gdb-minimal which provides gdb is to be removed. plasma-workspace depends on gdb-minimal | gdb; however: Package gdb-minimal is to be removed. Package gdb is not installed. Package gdb-minimal which provides gdb is to be removed. ... (trimmed output) This ends up doing what I wanted to do yesterday: I get full gdb instead of gdb-minimal, and my desktop environemnt doesn't disappear. The warning from dpkg seems a bit odd, looks like it also is confused about whether or not gdb is installed (and the warning also is printed twice...). Maybe I'll try booting up a full clean install in a VM to see if I can reproduce, to rule out that there is anything else which is messed up on my system. Either way, thanks a lot for your reply! Best regards, Morten
Re: removing gdb-minimal removed plasma-desktop?
On 2024-01-14 08:54 +0100, Morten Hauke Solvang wrote: > Short version: "apt remove gdb-minimal" seems to have also removed > plasma-desktop + a bunch of related packages. > > Curious if there are any good debugging tips for figuring out what > happened here. > Or maybe I'm missing something obvious about how apt works, and this > is expected behavior? > > Yesterday, I was trying to use gdb, and realized I had gdb-minimal > installed instead of the regular gdb package. > > To fix this, I first ran "apt remove gdb-minimal". > My assumption was that I then would have to run "apt install gdb". That assumption was a bit misguided. The correct way would have been to "apt install gdb" _without_ first removing gdb-minimal, that would have avoided the removal of reverse dependencies. > But turns out that invoking "gdb" after running "apt remove > gdb-minimal", I had the full version of gdb installed. > I didn't think more about it, went on using gdb and later shut down > the computer. > > When I booted it today, a different display manager than what I > usually have was shown. Switching to a different pseudoterminal and > checking "/var/log/apt/history.log" showed that when I had removed > gdb-minimal, for some reason plasma-desktop and some other packages > had also been removed. > > This is the entry I saw: > > Start-Date: 2024-01-13 15:52:49 > Commandline: apt remove gdb-minimal > Requested-By: morten (1000) > Install: gdb:amd64 (13.1-3, automatic), > libsource-highlight-common:amd64 (3.1.9-4.2, automatic), > libboost-regex1.74.0:amd64 (1.74.0+ds1-21, automatic), libc6-dbg:amd64 > (2.36-9+deb12u3, automatic), libbabeltrace1:amd64 (1.5.11-1+b2, > automatic), libsource-highlight4v5:amd64 (3.1.9-4.2+b3, automatic) > Remove: kinfocenter:amd64 (4:5.27.5-2), plasma-workspace:amd64 > (4:5.27.5-2+deb12u1), plasma-widgets-addons:amd64 (4:5.27.5-2), > plasma-workspace-wayland:amd64 (4:5.27.5-2+deb12u1), > sddm-theme-breeze:amd64 (4:5.27.5-2+deb12u1), > sddm-theme-debian-breeze:amd64 (4:5.27.5-2+deb12u1), gdb-minimal:amd64 > (13.1-3), kde-plasma-desktop:amd64 (5:142), plasma-desktop:amd64 > (4:5.27.5-2) > End-Date: 2024-01-13 15:52:52 > > (Looks like this is where regular gdb got installed too, so I didn't > actually have it, it just got autoinstalled when I removed > gdb-minimal?) Apparently, although it is not clear why because apt also went on to remove plasma-workspace and its reverse dependencies. The plasma-workspace package depends on gdb-minimal | gdb, that is why gdb-minimal was installed in the first place. > (Also, probably this info got printed when I ran "apt remove > gdb-minimal", and I was not paying attention.) Pretty sure not only was this information printed, apt also asks for confirmation if it has to install or remove more packages than requested. But it did what you told it to do, although the outcome might not have been what you desired. > To fix it, I ran this command and rebooted with "systemctl reboot", > which seems to have worked fine. Now I'm back in the expected desktop > environment. > apt install kinfocenter plasma-workspace plasma-widgets-addons > plasma-workspace-wayland sddm-theme-breeze sddm-theme-debian-breeze > kde-plasma-desktop plasma-desktop Good you sorted it out. The only question is why apt installed gdb even though it removed plasma-workspace anyway. When I tried to replicate your situation in a bookworm chroot, "apt remove gdb-minimal" removes plasma-workspace but does not install gdb. Cheers, Sven
removing gdb-minimal removed plasma-desktop?
Short version: "apt remove gdb-minimal" seems to have also removed plasma-desktop + a bunch of related packages. Curious if there are any good debugging tips for figuring out what happened here. Or maybe I'm missing something obvious about how apt works, and this is expected behavior? Yesterday, I was trying to use gdb, and realized I had gdb-minimal installed instead of the regular gdb package. To fix this, I first ran "apt remove gdb-minimal". My assumption was that I then would have to run "apt install gdb". But turns out that invoking "gdb" after running "apt remove gdb-minimal", I had the full version of gdb installed. I didn't think more about it, went on using gdb and later shut down the computer. When I booted it today, a different display manager than what I usually have was shown. Switching to a different pseudoterminal and checking "/var/log/apt/history.log" showed that when I had removed gdb-minimal, for some reason plasma-desktop and some other packages had also been removed. This is the entry I saw: Start-Date: 2024-01-13 15:52:49 Commandline: apt remove gdb-minimal Requested-By: morten (1000) Install: gdb:amd64 (13.1-3, automatic), libsource-highlight-common:amd64 (3.1.9-4.2, automatic), libboost-regex1.74.0:amd64 (1.74.0+ds1-21, automatic), libc6-dbg:amd64 (2.36-9+deb12u3, automatic), libbabeltrace1:amd64 (1.5.11-1+b2, automatic), libsource-highlight4v5:amd64 (3.1.9-4.2+b3, automatic) Remove: kinfocenter:amd64 (4:5.27.5-2), plasma-workspace:amd64 (4:5.27.5-2+deb12u1), plasma-widgets-addons:amd64 (4:5.27.5-2), plasma-workspace-wayland:amd64 (4:5.27.5-2+deb12u1), sddm-theme-breeze:amd64 (4:5.27.5-2+deb12u1), sddm-theme-debian-breeze:amd64 (4:5.27.5-2+deb12u1), gdb-minimal:amd64 (13.1-3), kde-plasma-desktop:amd64 (5:142), plasma-desktop:amd64 (4:5.27.5-2) End-Date: 2024-01-13 15:52:52 (Looks like this is where regular gdb got installed too, so I didn't actually have it, it just got autoinstalled when I removed gdb-minimal?) (Also, probably this info got printed when I ran "apt remove gdb-minimal", and I was not paying attention.) To fix it, I ran this command and rebooted with "systemctl reboot", which seems to have worked fine. Now I'm back in the expected desktop environment. apt install kinfocenter plasma-workspace plasma-widgets-addons plasma-workspace-wayland sddm-theme-breeze sddm-theme-debian-breeze kde-plasma-desktop plasma-desktop Looking back in history.log, the only other references to gdb-minimal and plasma-desktop I could find was near the top of the file (15th entry): Start-Date: 2024-01-08 06:25:16 Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -q -y -o APT::Install-Recommends=true -o APT::Get::AutomaticRemove=true -o Acquire::Retries=3 install task-kde-desktop bind9-dnsutils dbus systemd-timesyncd apt-listchanges reportbug netcat-traditional debian-faq python3-reportbug man-db ncurses-term bash-completion bind9-host groff-base mime-support manpages bzip2 inetutils-telnet doc-debian krb5-locales lsof ucf wget libnss-systemd ca-certificates gettext-base perl wamerican openssh-client xz-utils traceroute file liblockfile-bin libpam-systemd media-types task-english task-desktop task-ssh-server Install: ... I've cut off the "Install :" part, because it continues for more than a screen. It contains both the kde-packages which were gone from my system, and gdb-minimal. I assume that this is from when I ran the debian installer on monday (fresh install). I appreciate any input, thanks in advance.
Re: why gdb-doc is in non-free ??!
Alexander Villalba writes: > why gdb-doc is in non-free ??!: Because the GNU FDL does not grant the freedoms necessary for free software. > gdb-doc is also GNU The ‘gdb-doc’ work is released by the Free Software Foundation, and they intend it to be part of the GNU operating system. But, confusingly, the FSF do not consider that work to be free software (because they make an arbitrary and ill-defined distinction between documentation and software). https://en.wikipedia.org/wiki/GNU_Free_Documentation_License#Criticism> For a work to be included in Debian, this distinction is irrelevant: the work must satisfy the Debian Free Software Guidelines. Because the license restrictions do not grant the freedoms promised in the Debian Free Software Guidelines, the ‘gdb-doc’ work cannot be in Debian. -- \ “Every valuable human being must be a radical and a rebel, for | `\ what he must aim at is to make things better than they are.” | _o__) —Niels Bohr | Ben Finney
why gdb-doc is in non-free ??!
Dear Friends!: why gdb-doc is in non-free ??!: https://packages.debian.org/search?keywords=gdb-doc gdb-doc is also GNU
Re: I Couldn't install geany-plugin-gdb in jessie.
Hi.
On Wed, Feb 24, 2016 at 03:25:50PM +0800, EenyMeenyMinyMoa wrote:
> Thank you, Reco.
> After
> $ sudo apt-get install geany-plugin-debugger
> ,the Debug tab appeared at the below partof Geany.
Just as planned ;)
> In the "Build"/"Set Build Commands" menu, I've set
> compile: gcc -Wall -g -c "%f"
> build: gcc -Wall -g -o "%e" "%f"
Looks OK to me, as '-g' is there.
> I tried to do debugging the following code for a test.
>
> #include
> int main() {
> double x = 3;
> printf("%d ", x);
> return 0;
> }
>
> When I press the Run button in Debug tab,
> a message box appears saying
> "Error loading file".
Hm... I'm not familiar with Geany at all. It *may* be a way to tell you
that Geany is unable to launch gdb (which should have been installed
along the way). It may mean anything else of course.
This:
> the terminal output at that time :
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL'
> failed
> (geany:6702): GLib-CRITICAL **: g_hash_table_destroy: assertion
> 'hash_table != NULL' failed
Are usual signs of bad programming, this time at Geany side. These messages tell
that they try to free certain variables of type GString, but don't even
both try to check beforehand if said variable contain something.
What we see here is just a bunch unhandled assertions. By itself it may
mean anything.
> How can I do debugging in Geany successfully?
>
> And in the "Breakpoints" tab, an old breakpoint of a past file still remains.
> How can I delete this?
Beats me, sorry. I'd start the troubleshooting of this by attaching with
strace(1) to Geany's process - just to ensure whenever Geany is
actually tries to launch gdb.
Reco
Re: I Couldn't install geany-plugin-gdb in jessie.
Thank you, Reco.
After
$ sudo apt-get install geany-plugin-debugger
,the Debug tab appeared at the below partof Geany.
In the "Build"/"Set Build Commands" menu, I've set
compile: gcc -Wall -g -c "%f"
build: gcc -Wall -g -o "%e" "%f"
I tried to do debugging the following code for a test.
#include
int main() {
double x = 3;
printf("%d ", x);
return 0;
}
When I press the Run button in Debug tab,
a message box appears saying
"Error loading file".
the terminal output at that time :
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_string_free: assertion 'string != NULL' failed
(geany:6702): GLib-CRITICAL **: g_hash_table_destroy: assertion
'hash_table != NULL' failed
How can I do debugging in Geany successfully?
And in the "Breakpoints" tab, an old breakpoint of a past file still remains.
How can I delete this?
EenyMeenyMinyMoa
2016-02-22 16:38 GMT+08:00, Reco :
> Hi.
>
> On Mon, 22 Feb 2016 16:21:31 +0800
> EenyMeenyMinyMoa wrote:
>
>> Hi,
>> refering to
>>
>> https://packages.debian.org/search?lang=en&suite=all&searchon=names&keywords=geany-plugin-gdb
>>
>> I added the line
>> deb http://ftp.jp.debian.org/debian/ wheezy main
>> to /etc/apt/sources.list, and apt-get updated,
>> but I was not able to install geany-plugin-gdb.
>
> And you should not be able to as most of geany plugins depend on exact
> version of geany.
>
> This:
>
>> geany-plugin-gdb : Depends: geany-plugins-common (= 0.21.1.dfsg-4) but
>> 1.24+dfsg-5 is to be installed
>
> clearly shows us that you have installed geany from jessie, so the only
> kind of plugins that fit your install are geany plugins from Jessie.
>
>
>> What should I do?
>
> Try installing 'geany-plugin-debugger' instead.
>
>
>> And why isn't geany-plugin-gdb in the jessie repository?
>
> My guess is that they simply renamed the package.
>
> Reco
>
Re: I Couldn't install geany-plugin-gdb in jessie.
Hi. On Mon, 22 Feb 2016 16:21:31 +0800 EenyMeenyMinyMoa wrote: > Hi, > refering to > > https://packages.debian.org/search?lang=en&suite=all&searchon=names&keywords=geany-plugin-gdb > > I added the line > deb http://ftp.jp.debian.org/debian/ wheezy main > to /etc/apt/sources.list, and apt-get updated, > but I was not able to install geany-plugin-gdb. And you should not be able to as most of geany plugins depend on exact version of geany. This: > geany-plugin-gdb : Depends: geany-plugins-common (= 0.21.1.dfsg-4) but > 1.24+dfsg-5 is to be installed clearly shows us that you have installed geany from jessie, so the only kind of plugins that fit your install are geany plugins from Jessie. > What should I do? Try installing 'geany-plugin-debugger' instead. > And why isn't geany-plugin-gdb in the jessie repository? My guess is that they simply renamed the package. Reco
I Couldn't install geany-plugin-gdb in jessie.
Hi, refering to https://packages.debian.org/search?lang=en&suite=all&searchon=names&keywords=geany-plugin-gdb I added the line deb http://ftp.jp.debian.org/debian/ wheezy main to /etc/apt/sources.list, and apt-get updated, but I was not able to install geany-plugin-gdb. $ sudo apt-get install geany-plugin-gdb Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: geany-plugin-gdb : Depends: geany-plugins-common (= 0.21.1.dfsg-4) but 1.24+dfsg-5 is to be installed E: Unable to correct problems, you have held broken packages. What should I do? And why isn't geany-plugin-gdb in the jessie repository? EenyMeenyMinyMoa
Re: evolution segfaults except when run in gdb
On Sat, 03 Mar 2012 20:06:55 +0100, Steven Post wrote: > On Sat, 2012-03-03 at 17:23 +, Camaleón wrote: >> If the last thing you can see before it crashes is the IMAP syncing >> routine, have you tried to disable this account? > > After the first time I deleted all user information from my home dir > (~/.localshare/evolution and ~/.gconf/apps/evolution) and only added my > local mail spool (/var/mail), it still crashed with only that local > account. I don't know Evo enough to know where it stores the data for the accounts but if you're sure they're under those directories and you removed all their data, then fine. >> > The thing is, this doesn't happen on other accounts on this desktop, >> > re-installation doesn't work, and I already cleared all evolution >> > related settings and mail inside my home directory. It then runs >> > normally until I add an account, then it is back with the segfault. >> >> So the problem seems to be under your user's profile (have you tried to >> reset/restore it? > > Yes, see above. Well, I meant your _whole_ user desktop profile not just Evo's ;-), specifically your GNOME settings. >> What DE are you running? > > I'm running the testing distribution with gnome 3.2. Okay, then could it be a recent update that broke Evo? Review the list for the current open bugs (when it comes to Evo it uses to be a long one :-P): http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=evolution;dist=unstable >> ) or you're having problems >> with a specific account settings (it happens when you add any type of >> account -pop3, imap, local mailbox- or just crashes with one of them?). > > As soon as any account is added, it crashes. I haven't tried with pop3 > and some others, only with imap and local account. Just in case, I would also try also with POP3. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jiu6jv$q2j$1...@dough.gmane.org
Re: evolution segfaults except when run in gdb
On Sat, 2012-03-03 at 17:23 +, Camaleón wrote: > On Sat, 03 Mar 2012 13:14:10 +0100, Steven Post wrote: > > > Since the beginning of this week evolution crashes on my user account. > > Running from a terminal window I see all plugins getting loaded fine and > > it starts to sync my imap account, then is suddenly disappears with a > > segfault in the terminal window. > > If the last thing you can see before it crashes is the IMAP syncing > routine, have you tried to disable this account? After the first time I deleted all user information from my home dir (~/.localshare/evolution and ~/.gconf/apps/evolution) and only added my local mail spool (/var/mail), it still crashed with only that local account. > > > The thing is, this doesn't happen on other accounts on this desktop, > > re-installation doesn't work, and I already cleared all evolution > > related settings and mail inside my home directory. It then runs > > normally until I add an account, then it is back with the segfault. > > So the problem seems to be under your user's profile (have you tried to > reset/restore it? Yes, see above. > What DE are you running? I'm running the testing distribution with gnome 3.2. > ) or you're having problems > with a specific account settings (it happens when you add any type of > account -pop3, imap, local mailbox- or just crashes with one of them?). As soon as any account is added, it crashes. I haven't tried with pop3 and some others, only with imap and local account. > > > I tried to obtain some kind of backtrace as suggested on [1], by running > > evolution from gdb. But when I try this, evolution doesn't segfaults and > > I can work normally. > > It sounds like one of the Murphy's Laws: "a program never crashes when > you run it in debug mode" ;-( It seems that way :( > > Greetings, > > -- > Camaleón > > Kind regards, Steven signature.asc Description: This is a digitally signed message part
Re: evolution segfaults except when run in gdb
On Sat, 03 Mar 2012 13:14:10 +0100, Steven Post wrote: > Since the beginning of this week evolution crashes on my user account. > Running from a terminal window I see all plugins getting loaded fine and > it starts to sync my imap account, then is suddenly disappears with a > segfault in the terminal window. If the last thing you can see before it crashes is the IMAP syncing routine, have you tried to disable this account? > The thing is, this doesn't happen on other accounts on this desktop, > re-installation doesn't work, and I already cleared all evolution > related settings and mail inside my home directory. It then runs > normally until I add an account, then it is back with the segfault. So the problem seems to be under your user's profile (have you tried to reset/restore it? What DE are you running?) or you're having problems with a specific account settings (it happens when you add any type of account -pop3, imap, local mailbox- or just crashes with one of them?). > I tried to obtain some kind of backtrace as suggested on [1], by running > evolution from gdb. But when I try this, evolution doesn't segfaults and > I can work normally. It sounds like one of the Murphy's Laws: "a program never crashes when you run it in debug mode" ;-( Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jitk22$q2j$9...@dough.gmane.org
evolution segfaults except when run in gdb
Hi list, Since the beginning of this week evolution crashes on my user account. Running from a terminal window I see all plugins getting loaded fine and it starts to sync my imap account, then is suddenly disappears with a segfault in the terminal window. The thing is, this doesn't happen on other accounts on this desktop, re-installation doesn't work, and I already cleared all evolution related settings and mail inside my home directory. It then runs normally until I add an account, then it is back with the segfault. I tried to obtain some kind of backtrace as suggested on [1], by running evolution from gdb. But when I try this, evolution doesn't segfaults and I can work normally. Any Ideas on how to get any useful information on this? [1] http://wiki.debian.org/HowToGetABacktrace Kind regards, Steven signature.asc Description: This is a digitally signed message part
GDB and ld.so?
Hi folks, does anyone here know the magic incantation required to get GDB to accept a breakpoint within the loader (ld.so), in particular on dl_main(), on a x86_64 system? (gdb) set environment LD_PRELOAD /path/to/debug/ld.so (gdb) b dl_main (gdb) run ... does not seem to do the job. Thanks in advance, // Oliver -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101112183543.13...@gmx.net
How to use apache2-dbg with gdb
Hey all, I'm in the process of debugging a stange Apache+PHP related problem. (process taking cpu time, but strace -p $PID doesn't show anything for this process) I'd like to use gdb to look into the apache process and therefore installed the debugging symbols for apache2 (package apache2-dbg). How do I take advantage of those debugging symbols now? Is there an option to tell gdb to use those files as symbol sources? Thanks very much in advance, Christian -- Content Delivery Server u. Dienste Network Engineering & Design NETCOLOGNE Gesellschaft für Telekommunikation mbH Am Coloneum 9 | 50829 Köln Tel: 0221 -5751 | Fax: 0221 -75751 http://www.netcologne.de Geschäftsführer: Werner Hanf Dipl.-Ing. Karl-Heinz Zankel HRB 25580, AG Köln -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: How to have gdb step into a function from the application's shared library?
On Fri, Jul 17, 2009 at 11:34:40PM +, sobtwmxt wrote:
> Consider the following pseudo code:
>
>
> appLib.h
>
> int funcInAppLib(void);
>
>
> ::
> main.c
> ::
> #include "appLib.h"
>
> int main(void) {
> if (funcInAppLib() < 0) printf("funcInAppLib() < 0\n");
> }
>
>
> Where the application is debianized, and appLib is installed as a
> shared library. It has an associated -dev library, which is not
> normally installed.
>
> I want to have gdb step into funcInAppLib(). What should I do so
> that single step in main will actually step into funcInAppLib()? What
> I did so far is:
> 1) Make the deb without stripping debugging symbols.
> 2) Single step main() with gdb, by gdb s command. But that process
>skipped stepping into funcInAppLib().
You might want to install ddd (just to make it easier) and use it to
set a breakpoint at the start of the function before running the
program.
That still doesn't guarantee that the function is called. There can be
circumstances under which a function somehow gets "optimized away",
like getting inlined. In such a case, you might need to turn off all
optimization when compiling and/or put in some extra code for
debugging to the function being called.
I would change the code like that:
int main(void) {
int ret;
ret = funcInAppLib();
if(ret < 0) {
puts("funcInAppLib() < 0\n");
fflush(stdout);
}
}
Doing it step by step in the source like that can make it easier to
trace. Do the like in the function, and set a breakpoint in the
function.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
How to have gdb step into a function from the application's shared library?
Consider the following pseudo code:
appLib.h
int funcInAppLib(void);
::
main.c
::
#include "appLib.h"
int main(void) {
if (funcInAppLib() < 0) printf("funcInAppLib() < 0\n");
}
Where the application is debianized, and appLib is installed as a
shared library. It has an associated -dev library, which is not
normally installed.
I want to have gdb step into funcInAppLib(). What should I do so
that single step in main will actually step into funcInAppLib()? What
I did so far is:
1) Make the deb without stripping debugging symbols.
2) Single step main() with gdb, by gdb s command. But that process
skipped stepping into funcInAppLib().
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: gdb Q.: where do we stand regarding STL debugging?
On Tue, Mar 11, 2008 at 12:35:46AM -0400, "H.S." <[EMAIL PROTECTED]> was heard
to say:
> Just wanted to see if somebody could share some information about where
> we are regarding debugging programs which use STL.
>
> For example, I am not sure how I can print out the values of a two
> dimensional vector (vector of a vector) in gdb.
So, this isn't pretty. But you can examine the values of a vector in
gdb. If you print a vector you'll see something like this:
(gdb) print matchers
$10 =
{
>> = {
_M_impl = {> =
{<__gnu_cxx::new_allocator> = {}, }, _M_start = 0x832e4d8, _M_finish = 0x832e4e4,
_M_end_of_storage = 0x832e4e8}}, }
Here _M_start is matchers.begin(), _M_finish is matchers.end(), and I
think _M_end_of_storage is the end of the allocated space.
Luckily, gdb knows how to dispatch .size(), so you can do this to
print a vector:
(gdb) print [EMAIL PROTECTED]()
$9 = {0x832e4d8, 0x832e4e4, 0x832e4e8}
TBH, though, I think printf statements are more useful.
Daniel
PS: Please don't ask me about std::sets. ;-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gdb Q.: where do we stand regarding STL debugging?
Hi, Just wanted to see if somebody could share some information about where we are regarding debugging programs which use STL. For example, I am not sure how I can print out the values of a two dimensional vector (vector of a vector) in gdb. Printing out dynamically allocated memory works great, but I hit a wall when trying to examine queues or vectors. Also, what is the current conventional tool or approach to solve this problem? As far as I am concerned, at present I am using print statements (in gdb) for each component of a vector or queue to see if it contains the expected value. Time consuming, but I don't have to examine each location ... so kind of works. All insights regarding this are welcome. thanks, ->HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Using gdb on a debian system.
On Tue, Mar 20, 2007 at 03:13:20PM EST, Sven Arvidsson wrote: > On Mon, 2007-03-19 at 19:03 -0500, cga2000 wrote: > > > See http://wiki.debian.org/?HowToGetABacktrace > > > > I tried that HowTo but was unable to get it to work. > > > > It's also unclear what these commands do. > > > > Does this end up replacing the normal binaries with a debug version of > > the programs? > > Yes it does. > > > Where does the output of the "dpkg -i" go? > > Not sure what you mean here? > > > Am I supposed to reinstall the regular package when I'm done testing? > > You can do that if you want to. If you don't, the worst thing that > happens is that the application in question might run a little slower. > > > Is the source package that you download guaranteed to be in sync with > > the binary that was installed as a result of an "apt-get install"? > > Good question. I'm not entirely sure what happens if you run unstable > and stop upgrading after a while, I guess apt-get source will not find > the source package if it already has been replaced by something newer in > the archive? > > If that is so, you should be able to fetch the old source from > snapshot.debian.net. To be sure, compare the version numbers. > > > In any event, I had tried what the author of the doc recommends and was > > unable to get gdb to do anything apart from giving me the infamous > > "unable.." message. > > Is it a specific package you have trouble with? It might be a bug in the > package so it will be stripped of the debug info nevertheless. > > HTH, Certainly does. What it tells me is that I need to get a better understanding of what gdb does behind the scenes .. and _then_ figure out whether the options provided by apt can provide the necessary framework. What I'm driving at .. say .. I run into a problem with such and such application .. or I'm curious about how it does certain things.. so I take a look at the source .. but eventually, it turns out some things need clarification and one way to do that is to run the application under gdb to verify hunches/assumptions. Over the years, this might concern a number or packages and it may turn out that I need a debugging environment for a given application for six months .. a year .. and at the other end something so trivial that I won't need the environment more than for a couple of hours. Obviously I'd rather not pollute my "regular" environment with all these goings-on. So, maybe the correct way to go about doing this is maintaining a minimal debian system under a chroot and use that for debugging? Thanks, cga -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Using gdb on a debian system.
On Mon, 2007-03-19 at 19:03 -0500, cga2000 wrote: > > See http://wiki.debian.org/?HowToGetABacktrace > > I tried that HowTo but was unable to get it to work. > > It's also unclear what these commands do. > > Does this end up replacing the normal binaries with a debug version of > the programs? Yes it does. > Where does the output of the "dpkg -i" go? Not sure what you mean here? > Am I supposed to reinstall the regular package when I'm done testing? You can do that if you want to. If you don't, the worst thing that happens is that the application in question might run a little slower. > Is the source package that you download guaranteed to be in sync with > the binary that was installed as a result of an "apt-get install"? Good question. I'm not entirely sure what happens if you run unstable and stop upgrading after a while, I guess apt-get source will not find the source package if it already has been replaced by something newer in the archive? If that is so, you should be able to fetch the old source from snapshot.debian.net. To be sure, compare the version numbers. > In any event, I had tried what the author of the doc recommends and was > unable to get gdb to do anything apart from giving me the infamous > "unable.." message. Is it a specific package you have trouble with? It might be a bug in the package so it will be stripped of the debug info nevertheless. HTH, -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Re: Using gdb on a debian system.
On Mon, Mar 19, 2007 at 03:58:15AM EST, Sven Arvidsson wrote: > On Sun, 2007-03-18 at 23:53 -0500, cga2000 wrote: > > I have tried to follow the recommendations I found in various docs, > > like rebuilding the package via an "apt-get source package" followed > > by a "dpkg -i package_name" to no effect. > > > > Even if I try to point gdb to the directory that contains the source > > via the "-d" flag I end up with the dreaded "no symbols table loaded" > > message. "use the file command". > > The Debian packages are by default stripped of all debugging info. When > you rebuild the packages yourself, you can choose not to do so. It > should be much easier than grabbing the upstream source and building it. > > See http://wiki.debian.org/?HowToGetABacktrace I tried that HowTo but was unable to get it to work. It's also unclear what these commands do. Does this end up replacing the normal binaries with a debug version of the programs? Where does the output of the "dpkg -i" go? Am I supposed to reinstall the regular package when I'm done testing? Is the source package that you download guaranteed to be in sync with the binary that was installed as a result of an "apt-get install"? In any event, I had tried what the author of the doc recommends and was unable to get gdb to do anything apart from giving me the infamous "unable.." message. Mind you, I know how to run a debugging session with gdb but I don't know much about setting it up .. ie. I just write some buggy code, gcc it and do a "gdb ./buggy_prog .. and it's always worked. Maybe I should count my blessings and take this as a golden opportunity to learn a few things about setting up a gdb session. :-) Thanks, cga -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Using gdb on a debian system.
On Sun, Mar 18, 2007 at 11:07:04PM EST, Roberto C. Sánchez wrote: > On Sun, Mar 18, 2007 at 11:53:51PM -0500, cga2000 wrote: > > Could somebody advise on using gdb on a debian system? > > > > Currently whenever I need to take an insider look at what the code is > > really doing, I try to locate the source of the same version, download > > the .tar.gz .. run configure/make and execute the version that I built > > from source: > > > > $ gdb ./program > > > > Is there any way I could cause debian to systematically install the > > source that corresponds to the packaged binaries? > > > What you really need are the -dbg variants for your packages. Not all > packages have a -dbg variant available, but many of the bigger and more > popular packages do. The -dbg packages are compiled with extra > debugging information, allowing you to run them in gdb and get useful > information. Saw that but then, $ apt-cache search dbg | wc .. gives me just over 100 hits. And with 2-3 exceptions all of them are libraries. Seems I missed something? Thanks, cga
Re: Using gdb on a debian system.
Sven Arvidsson wrote: > See http://wiki.debian.org/?HowToGetABacktrace > Nice link! Explains the concepts and commands beautifully! Long live Debian Wiki and kudos to the authors! raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Using gdb on a debian system.
On Sun, 2007-03-18 at 23:53 -0500, cga2000 wrote: > I have tried to follow the recommendations I found in various docs, > like rebuilding the package via an "apt-get source package" followed > by a "dpkg -i package_name" to no effect. > > Even if I try to point gdb to the directory that contains the source > via the "-d" flag I end up with the dreaded "no symbols table loaded" > message. "use the file command". The Debian packages are by default stripped of all debugging info. When you rebuild the packages yourself, you can choose not to do so. It should be much easier than grabbing the upstream source and building it. See http://wiki.debian.org/?HowToGetABacktrace -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Re: Using gdb on a debian system.
On Sun, Mar 18, 2007 at 11:53:51PM -0500, cga2000 wrote: > Could somebody advise on using gdb on a debian system? > > Currently whenever I need to take an insider look at what the code is > really doing, I try to locate the source of the same version, download > the .tar.gz .. run configure/make and execute the version that I built > from source: > > $ gdb ./program > > Is there any way I could cause debian to systematically install the > source that corresponds to the packaged binaries? > What you really need are the -dbg variants for your packages. Not all packages have a -dbg variant available, but many of the bigger and more popular packages do. The -dbg packages are compiled with extra debugging information, allowing you to run them in gdb and get useful information. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Using gdb on a debian system.
Could somebody advise on using gdb on a debian system? Currently whenever I need to take an insider look at what the code is really doing, I try to locate the source of the same version, download the .tar.gz .. run configure/make and execute the version that I built from source: $ gdb ./program Is there any way I could cause debian to systematically install the source that corresponds to the packaged binaries? Couldn't find an option to "apt-get install" that does that. I have tried to follow the recommendations I found in various docs, like rebuilding the package via an "apt-get source package" followed by a "dpkg -i package_name" to no effect. Even if I try to point gdb to the directory that contains the source via the "-d" flag I end up with the dreaded "no symbols table loaded" message. "use the file command". IOW .. I can't do anything useful. Sorry, I'm only an occasional user of gdb .. but it does come in handy when you run into some cryptic piece of code and you'd like to see de visu what it might be doing. I have heard about "dbg" debs but there are not many of them in the usual sarge places/repositories. Any pointers or a quick explanation very welcome. The docs I found online were not very useful. Thanks, cga. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
No GDB stack traces after deadlock
I want to file the following bug report, but I'm not sure if it's a gdb,
libc6 or libc6-dbg problem:
Package: libc6
Version: 2.3.6.ds1-11
If you don't install libc6-dbg, and set LD_LIBRARY_PATH=/usr/lib/debug,
then you get corrupted stack traces for deadlocked threads in GDB:
$ cat deadlock.c
#include
int main(int argc, char** argv) {
pthread_mutex_t lock = PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_lock(&lock);
pthread_mutex_lock(&lock);
}
$ gcc -g -O0 deadlock.c -o deadlock -lpthread
$ gdb ./deadlock
...
(gdb) run
Starting program: /home/sears/deadlock/deadlock
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1209542976 (LWP 9659)]
// program hangs as expected, hit ^C
Program received signal SIGINT, Interrupt.
[Switching to Thread -1209542976 (LWP 9659)]
0xb7fd5410 in ?? ()
(gdb) where
#0 0xb7fd5410 in ?? ()
#1 0xbfee9698 in ?? ()
#2 0x0002 in ?? ()
#3 0x in ?? ()
(gdb)
libc6-dbg fixes the problem:
$ export LD_LIBRARY_PATH=/usr/lib/debug/
$ gdb ./deadlock
...
(gdb) run
^C
Program received signal SIGINT, Interrupt.
[Switching to Thread 16384 (LWP 10826)]
0xb7f63b64 in __pthread_sigsuspend (set=0xbfa040f8) at
../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c:54
54 ../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c: No such
file or directory.
in ../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c
(gdb) where
#0 0xb7f63b64 in __pthread_sigsuspend (set=0xbfa040f8)
at ../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c:54
#1 0xb7f62728 in __pthread_wait_for_restart_signal (self=0x804a8c0) at
pthread.c:1224
#2 0xb7f64fe6 in __pthread_alt_lock (lock=0xbfa04204, self=0x804a8c0)
at restart.h:34
#3 0xb7f621dc in *__GI___pthread_mutex_lock (mutex=0xbfa041f4) at
mutex.c:123
#4 0x080483ff in main () at deadlock.c:6
This has been driving me nuts for months, and I can't find it documented
anywhere. If this behavior is expected, the package description for
libc6-dbg needs to be updated:
> Contains unstripped shared libraries. This package is provided primarily to
> provide a backtrace with names in a debugger, this makes it somewhat easier
> to interpret core dumps. The libraries are installed in /usr/lib/debug and
> can be used by placing that directory in LD_LIBRARY_PATH. Most people will
> not need this package.
Otherwise, it's probably a bug in the libc6 package, or gdb.
Thanks,
Rusty
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gdb taking up all cpu
Hello, Since a couple of weeks I have had issues with gdb. Almost every time I step into a function gdb start taking all cpu. Is there anything I can tweaks so that it does not take too long. By default I use shared libs, and $ gcc --version gcc (GCC) 4.1.2 20060901 (prerelease) (Debian 4.1.1-13) and $ gdb --version GNU gdb 6.4.90-debian Thanks -- Mathieu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gdb not able to display the contents of source code
On 7/22/05, kamaraju kusumanchi <[EMAIL PROTECTED]> wrote: > David E. Fox wrote: > > >On Thu, 21 Jul 2005 13:00:18 -0400 > >kamaraju kusumanchi <[EMAIL PROTECTED]> wrote: > > > >>(gdb) list > >>1 ../sysdeps/i386/elf/start.S: No such file or directory. > >>in ../sysdeps/i386/elf/start.S > >>(gdb) > > > >I get the same output you do on a different small test program but it > >seems that the error doesn't cause a problem. For instance I can do a > >'break main' and then step line by line and am able to view the source, > >check the status of variables and so on. > > > Thanks. Now I at least know that it is reproducible. Just today morning, > I reported it to the BTS. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319520 list is probably breaking because the program's not running your code yet - it's in the fortran library's initialization code, and hasn't reached your code yet. Since you don't have a copy of the fortran library sources available, it breaks.
Re: gdb not able to display the contents of source code
David E. Fox wrote: On Thu, 21 Jul 2005 13:00:18 -0400 kamaraju kusumanchi <[EMAIL PROTECTED]> wrote: (gdb) list 1 ../sysdeps/i386/elf/start.S: No such file or directory. in ../sysdeps/i386/elf/start.S (gdb) I get the same output you do on a different small test program but it seems that the error doesn't cause a problem. For instance I can do a 'break main' and then step line by line and am able to view the source, check the status of variables and so on. Thanks. Now I at least know that it is reproducible. Just today morning, I reported it to the BTS. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319520 raju -- Kamaraju S Kusumanchi Graduate Student, MAE Cornell University http://www.people.cornell.edu/pages/kk288/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gdb not able to display the contents of source code
On Thu, 21 Jul 2005 13:00:18 -0400 kamaraju kusumanchi <[EMAIL PROTECTED]> wrote: > (gdb) list > 1 ../sysdeps/i386/elf/start.S: No such file or directory. > in ../sysdeps/i386/elf/start.S > (gdb) I get the same output you do on a different small test program but it seems that the error doesn't cause a problem. For instance I can do a 'break main' and then step line by line and am able to view the source, check the status of variables and so on. -- David E. Fox Thanks for letting me [EMAIL PROTECTED]change magnetic patterns [EMAIL PROTECTED] on your hard disk. --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gdb not able to display the contents of source code
$cat helloworld.f90 PROGRAM helloworld IMPLICIT NONE PRINT *, "Just for testing purposes" END PROGRAM helloworld $gfortran -g -Wall helloworld.f90 $./a.out Just for testing purposes $gdb ./a.out GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) list 1 ../sysdeps/i386/elf/start.S: No such file or directory. in ../sysdeps/i386/elf/start.S (gdb) Is this a (un)known bug? why is the list command not working? What am I doing wrong? Using Debian unstable, gfortran 4.0.1-2, kernel 2.6.9-1-686. TIA raju -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gdb + xfree86 (Cannot upgrade xfree to sarge)
[EMAIL PROTECTED] (Niels L. Ellegaard) writes: > In conclusion I am left with a system with no xserver. XFree86 > doesn`t start in Sarge and I cannot downgrade. As a final attempt > before reinstall I would like to start xfree86 in gdb, and see if I > can construct a backtrace. Perhaps this can give a hint of the > source of the problem. A small update. I recreated my old XF86Config file, so XFree86 4.0 works again, but I would still like debug XFree86 4.3 to find the source of the crash. I don't like the idea of ending up running an x-server that is older than stable :) Niels -- Niels L Ellegaard http://dirac.ruc.dk/~gnalle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gdb + xfree86 (Cannot upgrade xfree to sarge)
Is it possible to start xfree within gdb and get a backtrace? The problem is that if I try try `gdb Xfree86`, and my XFree86 crashes, then my screen locks, and I dont get to see the backtrace. OK here is the long story.. A year ago I filed a bug #204603 that I cannot upgrade XFree86 from Woody to Sarge. I still have this problem, and I am unable to use XFree86 with Sarge. When I try to start Xfree86 in Sarge I get a signal 11 crash with no further explanation. See Bug #204603 for log-files, search google for `gnalle debian XFree86` for a little more info (I cannot paste the links from emacs-w3 ). Last year I solved my problem by downgrading xserver-xfree86 to woody, and placing a line in my /etc/apt/preferences. This worked fine. Today I tried upgrading to Sarge again, and it still doesn`t work, but now I have the extra problem that I cannot downgrade again. The problem is that dkpg-reconfigure xserver-xfree86/stable requires a special version of discover, so I starting from a Sarge distribution it is no longer possible to downgrade xserver-xfree86 to woody. (I forgot to write down the exact eror message) In conclusion I am left with a system with no xserver. XFree86 doesn`t start in Sarge and I cannot downgrade. As a final attempt before reinstall I would like to start xfree86 in gdb, and see if I can construct a backtrace. Perhaps this can give a hint of the source of the problem. So returning to my original question. Is it possible to start XFree86 in gdb and get a backtrace? Thanks in advance Niels -- Niels L Ellegaard http://dirac.ruc.dk/~gnalle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
"gdb: Symbol `emacs_ctlx_keymap' has different size..."
Whenever I start gdb, I get the warning: % gdb --version gdb: Symbol `emacs_ctlx_keymap' has different size in shared object, consider re-linking GNU gdb 2002-04-01-cvs Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux". My system is % uname -ar Linux yow 2.4.18 #1 Sun Apr 4 17:45:51 EDT 2004 i686 unknown mostly stable distribution (including my gdb and emacs). In case it matters, my emacs is % emacs --version GNU Emacs 21.2.1 Copyright (C) 2001 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. If this is not a bug in the gdb package, what must I do to get rid of this error message? Thanks, kynn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gdb says gd2lib currupt in debian stable woody
I found this as well. http://www.zend.com/lists/php-dev/200110/msg01100.html It seems Debian is using the wrong versions of php and gd2; This is a valid security problem and needs to be fixed ASAP in debian stable. On 15 May 2004 at 13:38, [EMAIL PROTECTED] wrote: > I get the following any time I try to run a php script either from > apache or command line using the php gd2 function ImageCopy() under > debian stable (woody) > > cgi:/var/www/# php4 t.php > X-Powered-By: PHP/4.1.2 > Content-type: text/html > > > Segmentation fault > > > Everything else in gd2 works but for some reason the ImageCopy() > function in the php lib does not work at all, so I got out gdb and > ran some tests. > > cgi:/var/www/# gdb /usr/bin/php4 > GNU gdb 2002-04-01-cvs > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-linux"...(no debugging symbols > found)... > (gdb) set args -f /var/www/t.php > (gdb) set args -f /var/www/t.php > (gdb) run > Starting program: /usr/bin/php4 -f /var/www/t.php > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)...(no debugging symbols found)... > > (no debugging symbols found)... > Program received signal SIGSEGV, Segmentation fault. > 0x403b88d6 in gdImageCopy () from /usr/lib/libgd.so.2 > (gdb) quit > > > I apt-get removed the gd2 lib and installed the noxpm version, then > reinstalled php4-gd2 and the rest , they said they had to have the > normal version with xpm support so I let it do its thing. > > And so I ran the test again after it failed, and I get the exact same > thing. Is anyone else getting these errors? Everything else in gdlib > is working fine but its this one function that seems to be bad, using > the most updated and official libs available. > > If anyone has any ideas or has a way to fix this please let me know, > I am using only official packages. > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gdb says gd2lib currupt in debian stable woody
I get the following any time I try to run a php script either from apache or command line using the php gd2 function ImageCopy() under debian stable (woody) cgi:/var/www/# php4 t.php X-Powered-By: PHP/4.1.2 Content-type: text/html Segmentation fault Everything else in gd2 works but for some reason the ImageCopy() function in the php lib does not work at all, so I got out gdb and ran some tests. cgi:/var/www/# gdb /usr/bin/php4 GNU gdb 2002-04-01-cvs Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...(no debugging symbols found)... (gdb) set args -f /var/www/t.php (gdb) set args -f /var/www/t.php (gdb) run Starting program: /usr/bin/php4 -f /var/www/t.php (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x403b88d6 in gdImageCopy () from /usr/lib/libgd.so.2 (gdb) quit I apt-get removed the gd2 lib and installed the noxpm version, then reinstalled php4-gd2 and the rest , they said they had to have the normal version with xpm support so I let it do its thing. And so I ran the test again after it failed, and I get the exact same thing. Is anyone else getting these errors? Everything else in gdlib is working fine but its this one function that seems to be bad, using the most updated and official libs available. If anyone has any ideas or has a way to fix this please let me know, I am using only official packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gdb 6.0 (unofficial) backport from unstable to testing available?
On Sun, Feb 15, 2004 at 12:12:07PM +0100, Holger Rauch wrote: > Since gdb 6.0 has not yet officially made it into testing due to some > dependency problems, where can I find a backported version of gdb 6,0 > to Debian testing so that I can debug my program using gdb 6.0? Backports from unstable to testing rarely happen. However: gdb (5.3-2 to 6.0-6) Maintainer: Daniel Jacobowitz 11 days old (needed 10 days) out of date on hppa: gdb (from 5.3-2) Not considered The only reason gdb 6.0-6 isn't in testing is because hppa is having trouble with it; there's no reason you can't simply install unstable's gdb on testing. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gdb 6.0 (unofficial) backport from unstable to testing available?
Hello! I'm running Debian testing with kernel 2.6.2. When debugging programs with gdb 5.3, I get the following error messages: (gdb) r Starting program: /home/holgi/sara4-stuff/sas/xmlmodule/test-progs/sqltok+xqueryconv-test/tam_select-test_mg Error while reading shared library symbols: Cannot find new threads: capability not available Cannot find user-level thread for LWP 1377: capability not available This seems to be a known problem (googled for the error message) in conjunction with kernel 2.6.x and the advice is to use gdb 6.0. Since gdb 6.0 has not yet officially made it into testing due to some dependency problems, where can I find a backported version of gdb 6,0 to Debian testing so that I can debug my program using gdb 6.0? Thanks in advance for any info! Greetings, Holger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gdb: list command does not work inside libc6-dbg
I've installed libc6-dbg, and set LD_LIBRARY_PATH correctly. I've also gotten the source for libc6-dbg and unpacked both the tar.bz2 files inside it, and added the main dir, and all the subdirs with the dir command. When I set a breakpoint at __libc_write and do list, I get: (gdb) c Continuing. Breakpoint 1, 0x404423f0 in __libc_write () at __libc_write:-1 -1 __libc_write: No such file or directory. in __libc_write (gdb) l 1 in __libc_write What am I doing wrong? Need a new email address that people can remember Check out the new EudoraMail at http://www.eudoramail.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
GDB from unstable and GCC 3.1 (on x86)
GDB from unstable (x86) is unable to read debugging information generated by current GCC 3.1 CVS (using the "-g") switch. Is this a known problem? Are there any workarounds? I thought that GDB 5.1 finally supported DWARF2, which is needed by more recent GCC versions. -- Florian Weimer[EMAIL PROTECTED] University of Stuttgart http://CERT.Uni-Stuttgart.DE/people/fw/ RUS-CERT +49-711-685-5973/fax +49-711-685-5898
C++: a gdb problem when debugging multiple files source program.
For some reason the behavior of gdb when I split a C++ program into
multiple files is not the same as when there is only one source file.
In particular, in the multiple file case gdb does not recognize local
variables and does not honor breakpoints that are set by line numbers.
What am I missing?
The details are:
(gdb) b demo::demo()
Breakpoint 1 at 0x804d69c: file demo.cc, line 4.
(gdb) r
Starting program: /tmp/multipleFiles
Breakpoint 1, 0x0804d69c in demo (this=0x804cb64) at demo.cc:4
4 {
(gdb) l
1 #include "demo.h"
2
3 demo::demo()
4 {
5 ifstream input("mainMultiple.cc");
6 istream_iterator iter(input);
7 while (input) cout << *iter++ << " ";
8 cout << "\n";
9 };
10
(gdb) n
5 ifstream input("mainMultiple.cc");
(gdb) n
6 istream_iterator iter(input);
(gdb) p input
No symbol "input" in current context.
(gdb) b 8
Breakpoint 2 at 0x804d5f0: file demo.cc, line 8.
(gdb) c
Continuing.
#include "demo.h" int main() {}
Program exited normally.
(gdb) q
[02:49:37 tmp]$
gdb version is 5.1.
[02:50:20 tmp]$ g++-3.0 -v
Reading specs from /usr/lib/gcc-lib/i386-linux/3.0.2/specs
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,p
roto,objc --prefix=/usr --infodir=/share/info --mandir=/share/man
--enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib
--enable-long-long --enable-nls --without-included-gettext
--disable-checking --enable-threads=posix --enable-java-gc=boehm
--with-cpp-install-dir=bin --enable-objc-gc i386-linux
Thread model: posix
gcc version 3.0.2 (Debian)
[02:50:27 tmp]$
The build line from the Makefile is:
multipleFiles: demo.cc demo.h mainMultiple.cc
$(CXX) $(CXXFLAGS) $(LDFLAGS) -o $@ demo.cc mainMultiple.cc
Follows the sources for the multiple and single versions of the program
and the Makefile:
::
demo.h
::
#include
#include
#include
using namespace std;
class demo {
public:
demo();
};
extern demo testing;
::
demo.cc
::
#include "demo.h"
demo::demo()
{
ifstream input("mainMultiple.cc");
istream_iterator iter(input);
while (input) cout << *iter++ << " ";
cout << "\n";
};
demo testing;
::
mainMultiple.cc
::
#include "demo.h"
int main() {}
::
mainSingle.cc
::
#include
#include
#include
using namespace std;
class demo
{
public:
demo() {
ifstream input("mainSingle.cc");
istream_iterator iter(input);
while (input) cout << *iter++ << " ";
cout << "\n";
}
};
demo testing;
int main() {}
::
Makefile
::
CXX = g++-3.0
CXXFLAGS = -Wall -ggdb
LDFLAGS = -ggdb
all: multipleFiles singleFile
multipleFiles: demo.cc demo.h mainMultiple.cc
$(CXX) $(CXXFLAGS) $(LDFLAGS) -o $@ demo.cc mainMultiple.cc
singleFile: mainSingle.cc
$(CXX) $(CXXFLAGS) $(LDFLAGS) -o $@ $<
clean:
$(RM) -v *.o
.PHONY: all clean
--
Shaul Karl
email: shaulka(at-no-spam)bezeqint.net
Please replace (at-no-spam) with an at - @ - character.
(at-no-spam) is meant for unsolicitate mail senders only.
Re: Debugger DDD with gdb
As has been pointed out, your problem description isn't very clear. There could be a lot of reasons for 'failure.' To answer your other question - I like both insight and ddd. I don't know if insight will work with the debian stable distribution. On Wed, Oct 31, 2001 at 01:37:05PM -0500, [EMAIL PROTECTED] wrote: > Hi all. > > I have installed DDD, and it looks neet, however when I am stepping > thru a simple program it fails on an ifstreem. This same executable does not > fail when run from xterm. > > Is there an option that I missed to tell DDD not to fail when opening input > files? > Or is there a better graphical front end? > Maybe this is a limitation with GDB? > > I am running Stable version of Debian, using g++ > > Thanks! > > xucaen > > [EMAIL PROTECTED]
Re: Debugger DDD with gdb
On Wed, Oct 31, 2001 at 13:37:05 -0500, [EMAIL PROTECTED] wrote: > I have installed DDD, and it looks neet, however when I am stepping > thru a simple program it fails on an ifstreem. That's not a very clear description of your problem. I guess you're trying to step into a function call to a library function and that your executable has not been built against a debugging version of that library. If that's the case, you should use "Next" to treat such a call as one instruction rather than do "Step" and get "source not found" errors. > Is there an option that I missed to tell DDD not to fail when opening > input files? DDD does not fail. Just use "Finish" when you've stepped into a function for which you don't have the source and you'll end up outside of the function call. > Or is there a better graphical front end? Not that I'm aware of. There's "xxgdb", but that does not add much to gdb in my opinion. In unstable, ther are "gvd" and "kdbg" which I haven't used yet. DDD is very useful, but like every program, you need to invest time to learn how to use it. HTH, Ray -- "Text processing doesn't matter." Fortran. Larry Wall on common fallacies of language design
Re: DDD with gdb Answer
On Wed, Oct 31, 2001 at 02:17:21PM -0500, [EMAIL PROTECTED] wrote: > hmmm.. how do I get color syntax to work in vim 5.6.070-1?? > (I figure if I ask, I'll figure it out. ;-) I highly suggest getting vim 6. Try people.debian.org/~wakkerma for the debs. But you get it to work by putting this into your ~/.vimrc and starting vim by typing 'vim'. Not vi: syntax on -- Danie Roux *shuffle* Adore Unix
DDD with gdb Answer
Hi all... somehow just asking the questions enables me to figure out the answers! ;-) I had thought that in DDD, File=>Open also changed into directory but it does not. That's why the input failed. it couldn't find the file. It's working now that I run DDD from current directory.(instead of from fvwm menu, and I am certain that File=>Change Directory will work also) hmmm.. how do I get color syntax to work in vim 5.6.070-1?? (I figure if I ask, I'll figure it out. ;-) Thanks all!!! Xucaen
Re: Debugger DDD with gdb
On Wed, 31 Oct 2001 [EMAIL PROTECTED] wrote: > Hi all. > > I have installed DDD, and it looks neet, however when I am stepping > thru a simple program it fails on an ifstreem. This same executable does not > fail when run from xterm. > > Is there an option that I missed to tell DDD not to fail when opening input > files? > Or is there a better graphical front end? > Maybe this is a limitation with GDB? > > I am running Stable version of Debian, using g++ Probably this version of gdb is quite old. Newer 5.0 versiond of gdb and the corresponding ddd seem to work without troubles. -jwb
Debugger DDD with gdb
Hi all. I have installed DDD, and it looks neet, however when I am stepping thru a simple program it fails on an ifstreem. This same executable does not fail when run from xterm. Is there an option that I missed to tell DDD not to fail when opening input files? Or is there a better graphical front end? Maybe this is a limitation with GDB? I am running Stable version of Debian, using g++ Thanks! xucaen [EMAIL PROTECTED]
Re: ddd/kdb dep: gdb 5.0 ?
On Wed, Aug 15, 2001 at 17:41:14 -0700, 'cduck' Chris Grierson wrote: > is this something the gdb package maintainer should be notified about, or > the ddd/kdb ones or none of the above? As DDD maintainer I am aware of this, and stand by the dependency. While DDD may work with the gdb version in woody, the >= 5.0 recommendation was made upstream, and I see no reason to ignore it. The proper way to fix this is to get a newer gdb in woody. Ray -- Tevens ben ik van mening dat Nederland overdekt dient te worden.
ddd/kdb dep: gdb 5.0 ?
i did a woody install the other day and ddd and kdb both demand gdb 5.0, but the 'current' woody package is 4.18. i overrode the deps and things installed (dselect from the install script). is this something the gdb package maintainer should be notified about, or the ddd/kdb ones or none of the above? -chris grierson [ Structural Informatics Group ] [ Dept. of Biological Structure ] [ University of Washington ] [ 206.616.7356:office ] [ 206.795.4998:cell ]
Re: gdb (non-Debian specific)
on Mon, Jun 18, 2001 at 12:33:08AM -0700, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: > Does anyone know what sort of performance hit, if any, could be > expected from one or more users running gdb on a multi-user system? $ time gdb ...in conjunction with: $ uptime ...will give you an idea of runtime and load average. See also 'nice' and 'batch'. -- Karsten M. Self http://kmself.home.netcom.com/ What part of "Gestalt" don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Are these opinions my employer's? Hah! I don't believe them myself! pgpAKC8EMhNIy.pgp Description: PGP signature
Re: gdb (non-Debian specific)
On Mon, Jun 18, 2001 at 12:31:32AM -0700, [EMAIL PROTECTED] wrote: > Sorry, this is a bit OT, but this is the only place I know where there > are people who know their stuff so well. > > Does anyone know what sort of performance hit, if any, could be > expected from one or more users running gdb on a multi-user system? Don't imagine it'd be any different than multiple users running multiple programs in any other scenario. Though, the program being debugged will suffer a performance penalty. So attaching gdb to apache won't improve you pages served per second stats ;) -- Eric G. Miller
gdb (non-Debian specific)
Sorry, this is a bit OT, but this is the only place I know where there are people who know their stuff so well. Does anyone know what sort of performance hit, if any, could be expected from one or more users running gdb on a multi-user system? Get your own FREE E-mail address at http://www.linuxfreemail.com Linux FREE Mail is 100% FREE, 100% Linux, and 100% yours!
gdb (non-Debian specific)
Sorry, this is a bit OT, but this is the only place I know where there are people who know their stuff so well. Does anyone know what sort of performance hit, if any, could be expected from one or more users running gdb on a multi-user system? Get your own FREE E-mail address at http://www.linuxfreemail.com Linux FREE Mail is 100% FREE, 100% Linux, and 100% yours!
GDB: Cannot access memory at address 0x40017df0
Hi, this morning, I did the upgrade of bind, and because of that, my libc6 was upgraded. After that, I've been unable to run gdb on my favorite little program. Does this soudn familiar to anyone? (ie, the error: `Cannot access memory at address 0x40017df0'). After that, I upgraded my whole system (apt-get upgrade), so now all libraries are up-to-date (as wel as the .dev packages), but the error message stays. (Yes, I can put a breakpoint at the first line of the program, and still I get the same error message). $ gdb q GNU gdb 5.0 Copyright 2000 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (gdb) run Starting program: /home/users/r+d/central2/joost/config/q Cannot access memory at address 0x40017df0 $ ldd q libcrypt.so.1 => /lib/libcrypt.so.1 (0x40021000) libresolv.so.2 => /lib/libresolv.so.2 (0x4004e000) libldap.so.2 => /usr/lib/libldap.so.2 (0x4005f000) liblber.so.2 => /usr/lib/liblber.so.2 (0x40085000) libc.so.6 => /lib/libc.so.6 (0x4008f000) libnsl.so.1 => /lib/libnsl.so.1 (0x4019b000) libsasl.so.7 => /usr/lib/libsasl.so.7 (0x401b) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) libdb2.so.2 => /usr/lib/libdb2.so.2 (0x401bc000) libdl.so.2 => /lib/libdl.so.2 (0x4020) libpam.so.0 => /lib/libpam.so.0 (0x40203000) Thanks, joostje
Re: bug in gdb! it segfaults!
> > now whether gdb should let me print "pow(run.m*run.dr, 2)" or not, that's > > gdb segfaulting. a debugger should _NOT_ segfault, under any > > circumstances. > > Unless, there is a hardware problem, esp. memory, gdb will stress out > your memory more than most apps. Do a kernel compile work fine ? yes, in fact, i just compiled the kernel two days ago... > Have you tried the same on another machine ? interesting idea -- i'll give it a try. pete
Re: bug in gdb! it segfaults!
> > now whether gdb should let me print "pow(run.m*run.dr, 2)" or not, that's > gdb segfaulting. a debugger should _NOT_ segfault, under any > circumstances. Unless, there is a hardware problem, esp. memory, gdb will stress out your memory more than most apps. Do a kernel compile work fine ? Have you tried the same on another machine ? Mikr
Re: bug in gdb! it segfaults!
On Mon, Sep 18, 2000 at 12:35:03PM -0700, Jakob 'sparky' Kaivo wrote: > Peter Jay Salzman <[EMAIL PROTECTED]> writes: > > > > contact FSF or debian? > > bug-gdb@gnu.org And also "info gdb". There's a long section on how to report bugs. Cheers, Chris -- It is much easier to be critical than to be correct. -- Benjamin Disraeli
Re: bug in gdb! it segfaults!
Peter Jay Salzman <[EMAIL PROTECTED]> writes: > hello all, > > i'm debugging a c++ program, and found something very distressing: > > % gdb wellspring core > GNU gdb 19990928 > (warranty snipped) > This GDB was configured as "i686-pc-linux-gnu"... > Core was generated by `./wellspring'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/lib/libstdc++-libc6.1-2.so.3...done. > Reading symbols from /lib/libm.so.6...done. > Reading symbols from /lib/libc.so.6...done. > Reading symbols from /lib/ld-linux.so.2...done. > #0 0x804ced8 in GetPotential ([EMAIL PROTECTED], V=0x8053028, > wf=0x805b588) >at functions.cc:51 > 51 V[j] = -4.0L*PI*G*pow(run.m*run.dr, > 2.0L)*(run.sum1[j] + run.sum2[j]); > (gdb) p run.m*run.dr > $1 = 0.013599479808447117947299662577692603 > (gdb) p pow(run.m*run.dr, 2) > Segmentation fault (core dumped) > > now whether gdb should let me print "pow(run.m*run.dr, 2)" or not, that's > gdb segfaulting. a debugger should _NOT_ segfault, under any > circumstances. > > i feel gdb is the most important program besides the linux kernel and the > C/C++ compilers. this should be fixed. what should i do? > > contact FSF or debian? bug-gdb@gnu.org
bug in gdb! it segfaults!
hello all,
i'm debugging a c++ program, and found something very distressing:
% gdb wellspring core
GNU gdb 19990928
(warranty snipped)
This GDB was configured as "i686-pc-linux-gnu"...
Core was generated by `./wellspring'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libstdc++-libc6.1-2.so.3...done.
Reading symbols from /lib/libm.so.6...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0 0x804ced8 in GetPotential ([EMAIL PROTECTED], V=0x8053028,
wf=0x805b588)
at functions.cc:51
51 V[j] = -4.0L*PI*G*pow(run.m*run.dr,
2.0L)*(run.sum1[j] + run.sum2[j]);
(gdb) p run.m*run.dr
$1 = 0.013599479808447117947299662577692603
(gdb) p pow(run.m*run.dr, 2)
Segmentation fault (core dumped)
now whether gdb should let me print "pow(run.m*run.dr, 2)" or not, that's
gdb segfaulting. a debugger should _NOT_ segfault, under any
circumstances.
i feel gdb is the most important program besides the linux kernel and the
C/C++ compilers. this should be fixed. what should i do?
contact FSF or debian?
pete
linux
One world, one web, one program. -- Microsoft Ad Campaign_
Ein Volk, ein Reich, ein Fuhrer. -- Nazi Ad Campaign._.
<=>+/\/-=Prevent world domination, Install Linux today!=-\/\+<=>/v\
website coming soon as I get DSL[EMAIL PROTECTED] // \\
^^ ^^
The best way to accelerate a win95 system is at 9.81 m/s^2 rules
Re: [*] GDB question
Hello Zhang, On 10 Apr 2000, maths wrote: > by the way, where can i find good tutorial of GDB? > IMHO the info pages provide a pretty good introduction to gdb. But there may be far better documentation about it somewhere on the web. Regards, Daniel
Re: [*] GDB question
On Mon, Apr 10, 2000 at 03:45:31AM +0800, maths wrote: > hello everybody: > > i wrote all function in a .h file, and include it in a mian > file, then cc -g ... late i use gdb to debug, when i use > command "list", it just list the code in main file, how can > i list the codes in .h file, so i can inset a break point or > something else? > by the way, where can i find good tutorial of GDB? > > thank you verymuch! Most people do not put functions on a .h file. That is where headers go (function and global declerations). If you want to do this right, put those functions either in the main.c, or even better: move them all to it's own .c file, and make the .h only contain function declerations of those functions, then compile like so: gcc -g -c main.c -o main.o gcc -g -c util.c -o util.o gcc main.o util.o -o myprogram Then you can debug the program (-g ensures debugging code is included as you probably already know). You can set the break point by line number in util.c. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
[*] GDB question
hello everybody: i wrote all function in a .h file, and include it in a mian file, then cc -g ... late i use gdb to debug, when i use command "list", it just list the code in main file, how can i list the codes in .h file, so i can inset a break point or something else? by the way, where can i find good tutorial of GDB? thank you verymuch! ** zhang xiaolei Department of mathematics GuangZhou Normal University mailto: [EMAIL PROTECTED] **
Problem with ldso/gdb in potato
--- Begin Message --- BUG IN DYNAMIC LINKER ld.so: dynamic-link.h: 57: elf_get_dynamic_info: Assertion `! "bad dynamic tag"' failed! This seems to point towards ldso in my potato installation. However, ldso has been installed without problems. This error only seems to occur with gdb, all other programs run fine. Any ideas? José -- José L Gómez Dans PhD student Radar & Communications Group Department of Electronic Engineering University of Sheffield UK --- End Message ---
Re: need help with gdb
> > BTW: How come that there is a gdb dir under /usr/doc/ but there is not one > > under /usr/share/doc/ ? What is the exact policy about /usr/doc/ and > > /usr/share/doc/ ? > /usr/doc was the traditional location of the documentation. This has changed > since Debian tries to get conform to the File-Hierarchy-Standard (FHS) which > demands everything which is shareable (like docs) under /usr/share. > Then every package that does not have all its documentation in /usr/share/doc/ should be filed a bug against? Same goes for man pages and info files? Actually, is not this makes /usr/doc obsolete?
Re: need help with gdb
Hello > http://www.cs.utah.edu/~hamlet/lib/lessons/gdb/gdb/gdb.html [btw. thanks for this hint] > BTW: How come that there is a gdb dir under /usr/doc/ but there is not one > under /usr/share/doc/ ? What is the exact policy about /usr/doc/ and > /usr/share/doc/ ? /usr/doc was the traditional location of the documentation. This has changed since Debian tries to get conform to the File-Hierarchy-Standard (FHS) which demands everything which is shareable (like docs) under /usr/share. bye, -christian- -- Linux - the choice of the GNU generation. Join the Debian Project http://www.debian.org Christian Hammers * Oberer Heidweg 35 * D-52477 Alsdorf * Tel: 02404-25624 50 3C 52 26 3E 52 E7 20 D2 A1 F5 16 C4 C9 D4 D3 1024/925BCB55 1997/11/01
Re: need help with gdb
> Is there some online reference for gdb? I consulted a Linux programming book > but it did not help. I tried the command 'gdb licq core' but this got me > nowhere; no 'core' file is created. I have used gdb before but for some > reason, I cannot get it to work. Perhaps I have forgotten how to do this. > http://www.cs.utah.edu/~hamlet/lib/lessons/gdb/gdb/gdb.html Try searching the web for more. BTW: How come that there is a gdb dir under /usr/doc/ but there is not one under /usr/share/doc/ ? What is the exact policy about /usr/doc/ and /usr/share/doc/ ? [10:31:02 /tmp]$ ls -d /usr/doc/g* /usr/doc/gawk /usr/doc/gettext-base /usr/doc/groff /usr/doc/gcc/usr/doc/glimpse /usr/doc/gs /usr/doc/gconv-modules /usr/doc/gpm /usr/doc/gsfonts /usr/doc/gdb/usr/doc/grep /usr/doc/gv /usr/doc/gettext/usr/doc/grep-dctrl/usr/doc/gzip [10:31:07 /tmp]$ ls -d /usr/share/doc/g* /usr/share/doc/gcc/usr/share/doc/grep/usr/share/doc/gs /usr/share/doc/gconv-modules /usr/share/doc/grep-dctrl /usr/share/doc/gzip /usr/share/doc/gpm/usr/share/doc/groff [10:31:21 /tmp]$
need help with gdb
Is there some online reference for gdb? I consulted a Linux programming book but it did not help. I tried the command 'gdb licq core' but this got me nowhere; no 'core' file is created. I have used gdb before but for some reason, I cannot get it to work. Perhaps I have forgotten how to do this. thanks -- Andrew - GnuPG Public KeyID: 0x48109681 *we all live downstream*
Re: gdb and potato
On Mon, Nov 22, 1999 at 06:24:05PM -0800, Dave Wiard wrote: > I recently updated fully to potato and am having a slight annoyance with > GDB. Giving an 'n' command acts with the exact behavior of 's'. Does > anyone else have this problem? This is a real annoyance when attempting > to perform a strncpy() call where GDB steps me through the ASM files: [snip example] > or something of that nature. Could somebody help me out with this? I suspect this is the result of the changed declaration of str* functions. When you try to step into it, stepi, you should see the compiled assembler. HTH (some), B.
gdb and potato
I recently updated fully to potato and am having a slight annoyance with GDB. Giving an 'n' command acts with the exact behavior of 's'. Does anyone else have this problem? This is a real annoyance when attempting to perform a strncpy() call where GDB steps me through the ASM files: (gdb) 199 strncpy( cmd->args[k++], &command[j], ( j - i ) ); (gdb) strncpy () at ../sysdeps/alpha/strncpy.S:32 32 ../sysdeps/alpha/strncpy.S: No such file or directory. Current language: auto; currently asm (gdb) 39 in ../sysdeps/alpha/strncpy.S or something of that nature. Could somebody help me out with this? TIA Dave Wiard
gdb version in slink: 4.17-4.m68k.objc.threads.hwwp.fpu.gnat.3
What does the m68k mean in gdb? Is it only m68k, or what the heck does that mean??? Robert Varga
Re: g77/fort77 and gdb
On Tue, Sep 28, 1999 at 01:42:37PM +0100, H C Pumphrey wrote: > Does anyone know whether it is possible to get gdb to work with Fortran? The free software support for running Fortran under a debugger is pretty poor. > (g77 or fort77) The documentation says it should work (with certain > caveats e.g. you can't see data in a common block, which is more feature > in order to look at the code I get an error. For g77 it is: > ../../../../libf2c/libF77/main.c:46: No such file or directory > (which there certainly isn't) That's odd - I don't get that on a "Hello, world!" program here. I get the same error as with fort77. In any case... > while for fort77 it is: > Can't find a default source file Try setting a breakpoint on the first line of code and running - it works for me, although I don't get the same error you get with g77. What's happening is that gdb doesn't know about the startup code in lib[fg]2c and thinks the program starts in the main() in the library. Since it doesn't (or shouldn't) have any debugging information on this it complains. Once it gets into your code, which does have debugging information everything is as fine as it's likely to get. There is a program avalible on sunsite called f2c-stabs which is supposed to help with debugging - it runs within Emacs and attempts to paper over some of the cracks by knowing things about the way f2c generated code works. I don't think anyone has been interested enough to package it. -- Mark Brown mailto:[EMAIL PROTECTED] (Trying to avoid grumpiness) http://www.tardis.ed.ac.uk/~broonie/ EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/ pgp616N4goyJh.pgp Description: PGP signature
g77/fort77 and gdb
Greetings, Debian users,
Does anyone know whether it is possible to get gdb to work with Fortran?
(g77 or fort77) The documentation says it should work (with certain
caveats e.g. you can't see data in a common block, which is more feature
than bug IMHO). Both the systems I use are standard Debian 2.1 (slink). I
have tried the obvious:
${fort77,g77} -g foo.f
$gdb a.out
However if I then type
(gdb) list
in order to look at the code I get an error. For g77 it is:
../../../../libf2c/libF77/main.c:46: No such file or directory
(which there certainly isn't)
while for fort77 it is:
Can't find a default source file
I picked through the g77 docs and found the suggestion that I try
g77 -gstabs instead of g77 -g but that didn't work.
Any suggestions?
Many TIA
Hugh
==
Dr. Hugh C. Pumphrey | Tel. 0131-650-6026,Fax:0131-650-5780
Department of Meteorology| Replace 0131 with +44-131 if outside UK
The University of Edinburgh | Email [EMAIL PROTECTED]
EDINBURGH EH9 3JZ, Scotland | URL: http://www.met.ed.ac.uk/~hcp
===
Re: Why can't GDB or DDD find my source code?
That was it! Thanks a lot it's so nice when something turns out to be so simple! > Do you even have an executable file called 'foo' there? The -o option > should be immediately followed by the name (which, by your examples is > either -g or -ggdb). Try compiling with: > > $ gcc -g -o foo foo.c > > Matthew > Rich wrote: > > I am compiling a C program like so > > > > gcc -o -g foo foo.c > > > > alternatively > > > > gcc -o -ggdb foo foo.c > > > > When I run gdb, I get "(no debugging symbols found)" > > > > When I run ddd, I get "GDB cannot find the source code of your program"
Re: Whay can't GDB or DDD find my source code?
On Wed, Sep 15, 1999 at 12:15:49AM -0500, rich wrote: > I am compiling a C program like so > > gcc -o -g foo foo.c > > alternatively > > gcc -o -ggdb foo foo.c > > When I run gdb, I get "(no debugging symbols found)" Hmm. Can't help here. It looks like it to me, though I might suggest re-ordering your command line args -- gcc -h -o foo foo.c though I really doubt that will have any effect. > When I run ddd, I get "GDB cannot find the source code of your program" > I'm running everything from the same directory, and have tried gdb > ./foo, etc. When I tried ddd it took me several tries to get it to open the source code along with everything else. I can't remember if I specified the source on the command line, or if I had to edit the preferences to tell it where it could find the sources, or if I was screwing up the "file|open source" command. (Cool command name... :) > Am I just confused as to what these programs should be doing? At least > they should be able to find the source code, right? Unless there are no > errors, maybe? > > Baffled, > > Rich > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- Seth Arnold | http://www.willamette.edu/~sarnold/ Hate spam? See http://maps.vix.com/rbl/ for help Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
Re: Whay can't GDB or DDD find my source code?
Do you even have an executable file called 'foo' there? The -o option should be immediately followed by the name (which, by your examples is either -g or -ggdb). Try compiling with: $ gcc -g -o foo foo.c Matthew rich wrote: > > I am compiling a C program like so > > gcc -o -g foo foo.c > > alternatively > > gcc -o -ggdb foo foo.c > > When I run gdb, I get "(no debugging symbols found)" > > When I run ddd, I get "GDB cannot find the source code of your program" > > I'm running everything from the same directory, and have tried gdb > ./foo, etc. > > Am I just confused as to what these programs should be doing? At least > they should be able to find the source code, right? Unless there are no > errors, maybe? > > Baffled, > > Rich > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Whay can't GDB or DDD find my source code?
I am compiling a C program like so gcc -o -g foo foo.c alternatively gcc -o -ggdb foo foo.c When I run gdb, I get "(no debugging symbols found)" When I run ddd, I get "GDB cannot find the source code of your program" I'm running everything from the same directory, and have tried gdb ./foo, etc. Am I just confused as to what these programs should be doing? At least they should be able to find the source code, right? Unless there are no errors, maybe? Baffled, Rich
Re: glibc 2.1, gdb 4.18 and MT debugging ?
On Wed, Jun 02, 1999 at 04:53:46PM -0500, Oleg Krivosheev was heard to say: > > Hi, All > > just tried to debug my MT stuff using latest potato stuff and > did not succeed. Is MT debugging lost in transition? I was able > to debug my stuff on slink with glibc 2.0.7 and gdb 4.17 > > What package to blame: gdb 4.18, glibc 2.1 or kernel 2.2? > > thanks a lot for any help > > regards > > OK See http://www.debian.org/Bugs/db/37/37983.html Basically..potato's gdb doesn't have the threading patch (I think that there was also some brokenness when glibc2.1 was introduced) but the next upstream version is supposed to support Linux threading without a patch. You'll have to ask gdb's maintainer for more information I think.. Daniel -- THERE IS NO HOPE BUT US. THERE IS NO JUSTICE BUT US. ALL THAT IS, IS OURS. BUT WE MUST CARE. FOR IF WE DO NOT CARE, THEN WE DO NOT EXIST... -- Terry Pratchett, _Reaper Man_
glibc 2.1, gdb 4.18 and MT debugging ?
Hi, All just tried to debug my MT stuff using latest potato stuff and did not succeed. Is MT debugging lost in transition? I was able to debug my stuff on slink with glibc 2.0.7 and gdb 4.17 What package to blame: gdb 4.18, glibc 2.1 or kernel 2.2? thanks a lot for any help regards OK
Re: GDB & memory access failure
Hi again, now guess what! I tried another aproach i.e. i tried to enter: 'break main' or 'break someFunctionName' and it worked. And I can in ddd select a functionName (main/whatever) and with the name selected add a breakpoint (by pushing that button...). Well that makes me very happy and I'm not going to spend months why it doesn't work with line-numbers (i.e. break 50), maybe I'll stumble overit someday. Hope I haven't wasted anyone's time regards - Ingvaldur Ingvaldur Þ. Sigurjonsson wrote: > > Hi, > > I am still having problem using the gdb-GNU debugger. > > The problem is that, that the breakpoints I set in the code, cannot be > inserted by the debugger. Here's an output from the gdb: > > > debbie:/home/ingi/misc/c++> gdb pdbg > GNU gdb 4.17.19981224.m68k.objc.threads.hwwp.fpu.gnat > ... > This GDB was configured as "i686-pc-linux-gnu"... > (gdb) break 50 > Breakpoint 1 at 0xb9c0: file pdbg.cpp, line 50. > (gdb) run > Starting program: /home/ingi/misc/c++/pdbg > Breakpoint 1 at 0x821e5f4: file pdbg.cpp, line 50. > Cannot insert breakpoint 1: > Cannot access memory at address 0x821e5f4. > (gdb) > > > The same result's apply for both me as a user and as a 'root'. > The code is ofcourse compiled with '-g' and this is my compiler: > Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs > gcc version egcs-2.91.66 Debian GNU/Linux (egcs-1.1.2 release) > > All programs are installed from debian-packages (potato). > > I'm not complaining for this otherwise wonderfully free packages, I'm > sure this can be fixed but I myself have been trying now for some weeks > but I now have to resign. > > Best regards > > -- Ingvaldur > ---C++--- > [EMAIL PROTECTED] | C++ > [EMAIL PROTECTED] | Linux on the Laptop Rulez... C++ > C > > P.S. > I have as an alternative written a PrintBlob( void* aData, int aSize ) > function which dump's memory in following format: > 6f 6e 73 73 6f 6e 20 31 39 36 35 2d 30 36 2d 32 onsson 1965-06-2 > 39 20 45 6c 69 74 20 4c 6f 67 69 6b 20 44 61 74 9 Elit Logik Dat > > but it would be nice with a nice debugger with a nice front-end > (ddd/xxgdb). > > :-) > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- ---C++--- [EMAIL PROTECTED] | http://elvis.elit.se/~ingi C++ [EMAIL PROTECTED] | Linux on the Laptop Rulez... C++ C
GDB & memory access failure
Hi, I am still having problem using the gdb-GNU debugger. The problem is that, that the breakpoints I set in the code, cannot be inserted by the debugger. Here's an output from the gdb: debbie:/home/ingi/misc/c++> gdb pdbg GNU gdb 4.17.19981224.m68k.objc.threads.hwwp.fpu.gnat ... This GDB was configured as "i686-pc-linux-gnu"... (gdb) break 50 Breakpoint 1 at 0xb9c0: file pdbg.cpp, line 50. (gdb) run Starting program: /home/ingi/misc/c++/pdbg Breakpoint 1 at 0x821e5f4: file pdbg.cpp, line 50. Cannot insert breakpoint 1: Cannot access memory at address 0x821e5f4. (gdb) The same result's apply for both me as a user and as a 'root'. The code is ofcourse compiled with '-g' and this is my compiler: Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 Debian GNU/Linux (egcs-1.1.2 release) All programs are installed from debian-packages (potato). I'm not complaining for this otherwise wonderfully free packages, I'm sure this can be fixed but I myself have been trying now for some weeks but I now have to resign. Best regards -- Ingvaldur ---C++--- [EMAIL PROTECTED] | C++ [EMAIL PROTECTED] | Linux on the Laptop Rulez... C++ C P.S. I have as an alternative written a PrintBlob( void* aData, int aSize ) function which dump's memory in following format: 6f 6e 73 73 6f 6e 20 31 39 36 35 2d 30 36 2d 32 onsson 1965-06-2 39 20 45 6c 69 74 20 4c 6f 67 69 6b 20 44 61 74 9 Elit Logik Dat but it would be nice with a nice debugger with a nice front-end (ddd/xxgdb). :-)
GDB/xxgdb segfaults!
Hi, When I try to debug an app, which does use some shared libraries, with ddd/gdb/xxgdb the gdb segfault's when it's launched by the gdb frontends. When launched from DDD, a dialog pops up saying "GDB could not be started.", and gives the "Exit", "Help" alternatives. The last message in DDD is: Running GDB (pid 505, tty /dev/pts/0)...Segmentation fault. The /dev/pts directory exists and everybody now have a rw on it. This is the line from /etc/fstab none /dev/pts devpts rw,gid=5,mode=620 0 0 and this is the line from /etc/mtab devpts /dev/pts devpts rw,gid=5,mode=620 0 0 after boot. I'm running the lates potato/ddd/2.2.5 Please advise -- Ingi ---C++--- [EMAIL PROTECTED] | C++ [EMAIL PROTECTED] | Linux on the Laptop Rulez... C++ C
Help! ddd says: "gdb: cannot open master pty"
Hi, I'm trying to run ddd on a Debian box, and I get the following message if I'm not root: bash-2.01$ ddd gdb: cannot open master pty: No such file or directory gdb: communication setup failed ddd starts, but the gdb prompt never appears. If I'm root, things work just fine. If I start gdb alone (even as non root), things work also. The ddd I use is ddd-smotif, and the box is mostly hamm, but as I had this problem, I thought on updating those packages (ddd and gdb) to slink, but that did not help. Any clue? Thanks, -- Luiz Otavio L. ZorzellaComputer Engineer [EMAIL PROTECTED]
GDB Problems
I have recently been expriencing problems with GDB. I will compiling a program with the -g symbol and run it in gdb. After setting a break point(typically line one worked in the past) and running the program I get this: Cannot insert breakpoint 1: Cannot access memory at address: some memory address I have been getting this error since I reinstalled linux. Is this a bad setting I've encountered or something else? Perhaps I've overlooked something. Any help in fixing this would be appreciated. Philip Thiem -- PENQUIN-LOVER-CODER ALERT: [EMAIL PROTECTED] All windows user please exvacuate the building (So I can install a better OS on the comps) Pass on the GAS get NASM instead.
Re: GDB problems
> Breakpoint 1 at 0xbab4: file program.c, line 4. > (gdb) r > Starting program: /home/IA/baptista/./program > Breakpoint 1 at 0x81f6c80: file program.c, line 4. > Cannot insert breakpoint 1: > Cannot access memory at address 0x81f6c80. > > Regards,Paulo Henrique > I started getting this error as well right after upgrading a number of packages to potato from slink. Glad to know it isn't me losing my mind, but a solution would be wonderful. I have yet to find one :( SJG
Re: GDB problems
Hi Henning,
thank you for you help. But it didnt work. See bellow.
[EMAIL PROTECTED]: ~$ more program.c
#include
void main()
{
int i=1;
printf("%d", i);
}
[EMAIL PROTECTED]: ~$ gcc -o program -g program.c
[EMAIL PROTECTED]: ~$ gdb ./program
GNU gdb 4.17.19981224.m68k.objc.threads.hwwp.fpu.gnat
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(gdb) l
1 #include
2 void main()
3 {
4 int i=1;
5 printf("%d", i);
6 }
(gdb) b 4
Breakpoint 1 at 0xbab4: file program.c, line 4.
(gdb) r
Starting program: /home/IA/baptista/./program
Breakpoint 1 at 0x81f6c80: file program.c, line 4.
Cannot insert breakpoint 1:
Cannot access memory at address 0x81f6c80.
Regards,Paulo Henrique
Quoting Henning Makholm ([EMAIL PROTECTED]):
> Paulo Henrique Baptista de Oliveira <[EMAIL PROTECTED]> writes:
>
> > [EMAIL PROTECTED]: /home/IA/baptista$ gcc -g -o teste teste.c
> > [EMAIL PROTECTED]: /home/IA/baptista$ gdb teste
> [...]
> > (gdb) l
> > warning: Source file is more recent than executable.
>
> This suggests that there is a 'teste' executable somewhere in
> your path that gdb finds before it looks for the one you just
> built.
>
> Try starting gdb with './teste' as the argument and see if it
> works better that way.
>
> --
> Henning Makholm
> http://www.diku.dk/students/makholm
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
Re: GDB problems
Paulo Henrique Baptista de Oliveira <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED]: /home/IA/baptista$ gcc -g -o teste teste.c > [EMAIL PROTECTED]: /home/IA/baptista$ gdb teste [...] > (gdb) l > warning: Source file is more recent than executable. This suggests that there is a 'teste' executable somewhere in your path that gdb finds before it looks for the one you just built. Try starting gdb with './teste' as the argument and see if it works better that way. -- Henning Makholm http://www.diku.dk/students/makholm
GDB problems
Hi Debian users,
I have some problems with gdb. Bellow I put the error that occurs when I
try to insert a breakpoint using gdb:
[EMAIL PROTECTED]: /home/IA/baptista$ more teste.c
#include
void main()
{
int i=1;
printf("%d", i);
}
[EMAIL PROTECTED]: /home/IA/baptista$ gcc -g -o teste teste.c
[EMAIL PROTECTED]: /home/IA/baptista$ gdb teste
GNU gdb 4.17.19981224.m68k.objc.threads.hwwp.fpu.gnat
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(gdb) l
warning: Source file is more recent than executable.
1 #include
2 void main()
3 {
4 int i=1;
5 printf("%d", i);
6 }
(gdb) b 5
Breakpoint 1 at 0xbab4: file teste.c, line 5.
(gdb) r
Starting program: /home/IA/baptista/teste
Breakpoint 1 at 0x81f6c30: file teste.c, line 5.
Cannot insert breakpoint 1:
Cannot access memory at address 0x81f6c30.
(gdb)
What is wrong?
The version of my gdb is of 4.17.199812.
Have a nice day,Paulo Henrique
Re: GDB and ADA.
> > What is the best way to have hamm system support debugging of ADA programs > > in > > gdb ? > > Install the slink version of gdb, try if it works; if it doesn't, submit a > useful bug report. > >dists/unstable/main/binary-i386/devel/gdb_4.17-4.m68k.objc.threads.hwwp.fpu.gn at.deb > Note the "gnat" in there. [23:02:45 shaul]$ zcat /usr/doc/gdb/changelog.Debian.gz | head -n 16 | tail * re-integrated gnat support. (Was repported as a bug against 4.16, patch had been integrated then, but dropped while switching to version 4.17). (NB: Not being an ADA expert, I'd appreciate if s/o could confirm it now works properly, thanx) -- Vincent Renardias <[EMAIL PROTECTED]> Fri, 3 Jul 1998 18:46:28 +0200 [23:03:05 shaul]$ I am only at the beginning of my ADA course, and my gdb knowledge is limited to the basic operations. But it seems to me that gdb support for ADA is working (at least the basic functionality). Please note that I didn't thoroughly test it, though. I'll submit a bug report if I'll encounter one. -- System Information Package: gdb Version: 4.17-4.m68k.objc.threads.hwwp.fpu.gnat Debian Release: 2.0 Kernel Version: Linux rakefet 2.0.34 #2 Thu Jul 9 10:57:48 EST 1998 i586 unknown Versions of the packages gdb depends on: ii libc6 2.0.7t-1 The GNU C library version 2 (run-time files) ii libreadlineg2 2.1-10.1 GNU readline and history libraries, run-time ii ncurses3.4 1.9.9g-8.8 Video terminal manipulation - shared librari
Re: GDB and ADA.
On Sun, Oct 18, 1998 at 08:21:26AM +0200, shaul wrote: > I tried to look for slink's gdb. All I could find is some m68k staff. (I > did find some relevant lines in Contents-i386.gz) What did I miss ? dists/unstable/main/binary-i386/devel/gdb_4.17-4.m68k.objc.threads.hwwp.fpu.gnat.deb Note the "gnat" in there. HTH, Ray -- J.H.M. Dassen | RUMOUR Believe all you hear. Your world may [EMAIL PROTECTED] | not be a better one than the one the blocks | live in but it'll be a sight more vivid. | - The Hipcrime Vocab by Chad C. Mulligan
Re: GDB and ADA.
I tried to look for slink's gdb. All I could find is some m68k staff. (I did find some relevant lines in Contents-i386.gz) What did I miss ? > > > What is the best way to have hamm system support debugging of ADA programs > > in > > gdb ? > > Install the slink version of gdb, try if it works; if it doesn't, submit a > useful bug report. >
Re: GDB and ADA.
On Wed, Oct 14, 1998 at 11:30:28PM +0300, shaul wrote: > It seems to me that hamm's version of gdb doesn't support debugging of ADA > programs. > Will that be changed in slink? >From the changelog in slink's gdb: * re-integrated gnat support. (Was repported as a bug against 4.16, patch had been integrated then, but dropped while switching to version 4.17). (NB: Not being an ADA expert, I'd appreciate if s/o could confirm it now works properly, thanx) > What is the best way to have hamm system support debugging of ADA programs in > gdb ? Install the slink version of gdb, try if it works; if it doesn't, submit a useful bug report. HTH, Ray -- Tevens ben ik van mening dat Nederland overdekt dient te worden.
