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
> dimensi
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/star
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
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 e
[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 gi
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 t
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
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
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 o
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
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 ca
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 s
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
> 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
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.m6
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
> > 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 t
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 "gn
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;
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
On Tue, May 19, 1998 at 11:52:24PM +0300, shaul wrote:
> > On Sun, 17 May 1998, Pete Poff wrote:
> >
> > > I'm using the "-g" flag. But gdb will tell me what code is causing the
> > > crash right?
> > >
> > > Thanks,
> > >
> >
> > It will depend. If the binary is stripped, you might not get m
> On Sun, 17 May 1998, Pete Poff wrote:
>
> > I'm using the "-g" flag. But gdb will tell me what code is causing the
> > crash right?
> >
> > Thanks,
> >
>
> It will depend. If the binary is stripped, you might not get much
> information out of it.
What is a stripped binary ? What are the ot
when you start gdb, issue a 'break main' instruction BEFORE you issue the
run command ... You can then 'step' (or 's') through the program and find
out where exactlty the error occured
--Jon
> Pete Poff <[EMAIL PROTECTED]> writes:
>
> > When I try out gdb on my program, all I can get is 'Prog
>
> I'm using the "-g" flag. But gdb will tell me what code is causing the
> crash right?
Maybe. The error you got, a segmentation fault, means that you tried
to access an illegal memory address. It could be that you wrote beyond
the limits of an array, or made an error in memory allocation.
Pete Poff <[EMAIL PROTECTED]> writes:
> When I try out gdb on my program, all I can get is 'Program recieved
> signal SIGSEGV, Segmentation fault.
> 0x8096baa in ? ().
> Does anyone know how I can use that to find out what code is causing the
> crash? I've read the helps, but can seem to what to
No, those packages are still in Incoming on master.
Shaya
On Mon, 14 Jul 1997, Ulf Jaenicke-Roessler wrote:
>
> Hi,
>
> I installed gdb_4.16-10 from unstable. It depends on ncurses-3.4 and
> libreadlineg2. However, there are no such packages.
> Is this a bug or are these packages missing a
>
> Hi,
>
> I installed gdb_4.16-10 from unstable. It depends on ncurses-3.4 and
> libreadlineg2. However, there are no such packages.
> Is this a bug or are these packages missing at the moment?
neighter. They are just still sitting in "incoming".
I've put those packages in
ftp://rulcmc.
Matthew Tebbens <[EMAIL PROTECTED]> writes:
>
> Can someone recommend a good GUI interface to GDB ?
>
Get 'ddd'. It's available as a debian package as well.
--
Kevin Hilman -- [EMAIL PROTECTED]
Sysadmin - Image Computing Systems Lab - U of Washington
PGP public key at h
>
>
> Can someone recommend a good GUI interface to GDB ?
> I see there are programs like TGDB and XXGDB, but they seem to be old and
> outdated. Maybe someone here is using, and can recommend a good GUI to
> GDB.
Try ddd-2.1 from devel. It is compiled with lesstif and might not be
really usable
On Wed, 15 Jan 1997 16:46:46 PST Richard Sevenich ([EMAIL PROTECTED]
i.org) wrote:
> Having updated to Debian 1.2.1, I get a new warning upon invoking gdb:
>
> 'warning: Unable to find dynamic linker breakpoint function'
>
> This doesn't cause problems for me, but maybe for someone else. Any
>
>
> I guess ld-linux.so is a special case - we can provide it unstripped.
>
> Thanks
>
How about this patch? It should make everyone happy. BTW, I am using
binutils 2.7.0.3.
--
H.J. Lu ([EMAIL PROTECTED])
---
Index: linux/ld-so/Config.mk
diff -c linux/ld-so/Config.mk:1.1.1.1 linux/ld-s
From: [EMAIL PROTECTED] (H.J. Lu)
> How do you debug a stripped binary? Unless I am wrong, if you want
> to debug ld-linux.so.1, you have to compile it with -g and don't strip
> it. It doesn't cost much in disk space.
I think he was making the point that the .dynsym section is present in
"strippe
Note that I am stripping all executables on the base floppies (to get them
to fit). This means if ld-linux.so has to be unstripped, simply changing
the package won't be enough. You have to tell me to fix it in the install
floppy set.
Thanks
Bruce
--
Bruce Perens K6BP [EMAIL PROT
H.J. Lu writes:
> > Douglas Bates writes:
> > > I have version 4.16-2 of the gdb package installed. When I start gdb
> > > I get the warnings
> > > warning: Unable to find dynamic linker breakpoint function.
> > > warning: GDB will be unable to debug shared library initializers
> > > warning: a
34 matches
Mail list logo
