I couldn't immediately find much of a description of how the record mechanism
works. Does it just interpret or single-step, recording overwritten values?
Something cleverer? Even if it just interprets, presumably I end up with a
separate log for each thread. If I can reverse-single-step
There may be an easy GC-specific workaound, int that you can probably build it
with -DNO_GETCONTEXT. Or you might be able to link statically against libc?
But this doesn't sound like this will be the last such problem. It sounds to
me like these things really need to get fixed in gdb.
Hans
I used gdb-6.8 on Ubutu 9.04. and I type this
in gnome-terminal :
gdb -q myprog
list
but it displays :
1 ../sysdeps/i386/elf/start.S: No such file or directory.
in ../sysdeps/i386/elf/start.S
Please help me.
Regards
Sarun
(sorry for my english, I'm not strong with it)
Hi,
got the error incomplete type for a non typedefed class.
How can I yvoid this ud get the class information ?
thx
Clemens
___
bug-gdb mailing list
bug-gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gdb
I have run a script and I dont want gdb to manually press enter all
the time
---Type return to continue, or q return to quit---
due to this , teh script is asking me to press thousands of enters,
whenevr it stops
can this be done with
the script is something like the following
while (1)
cont
On Sep 8, 2:34 pm, parag parag.p...@gmail.com wrote:
I have run a script and I dont want gdb to manually press enter all
the time
---Type return to continue, or q return to quit---
due to this , teh script is asking me to press thousands of enters,
whenevr it stops
can this be done with
Running GDB on netbsd it prints this message:
# gdb --write /netbsd
warning: offsetof (struct sigcontext, sc_pc) yields 92 instead of 44.
Please report this to bug-gdb@gnu.org.
warning: offsetof (struct sigcontext, sc_sp) yields 104 instead of 56.
Please report this to bug-gdb@gnu.org.
GNU gdb
Hello,
I assume I should be able to build GDB 6.8 for native (ie: non-Cygwin)
WinVista SP2 support using a mingw version og gcc. I was trying to
diagnose a problem I encountered with an environment that used the
original official release of GDB 6.8 for i686-pc-cygwin that came with
Hello,
I am experiencing trouble with GDB 6.8-debian through emacs 22.2.1 while
casting a pointer to an array using convenience variables to indicate
its dimensions.
As an example, I have defined variables $lines and $columns.
(gdb) set $lines = 6
(gdb) set $columns = 6
I have an 6x6 array of
Date: Wed, 4 Mar 2009 12:00:48 -0500
From: bug-gdb-requ...@gnu.org
Subject: bug-gdb Digest, Vol 70, Issue 2
To: bug-gdb@gnu.org
Send bug-gdb mailing list submissions to
bug-gdb@gnu.org
To subscribe or unsubscribe via the World Wide Web, visit
Hi Roger,
This is not the right place to get help about your flicker problem. I
suggest trying a graphics or X Window forum...
Just one tip though (from a developer with little experience in graphics
programming):
El lun, 02-03-2009 a las 11:00 -0500, Roger Moore escribió:
Please note that
I posted a request for help compiling on a Dec OSF 4.0F a week or so ago but
never heard anything back. Has anyone got gdb running on a DEC?
Thanks,
Marc
___
bug-gdb mailing list
bug-gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gdb
The screen in my app draws correctly, and stays drawn as expected;
however, when I attempt to move graphics on the screen, I starts to
flicker in an annoying way.
The default drawing mode in the application I am writing software for is
COPY, which is where the flicker occurs. If I change
I had some trouble compiling gdb 6.8 with gcc (2.95/3.2.2/4.0.2) on a Dec OSF
4.0f system. I was able to get around this by turning of -Werror in the
makefile, but when I try running make check it immediately fails with an
error on test-demangle. Here is the error:
# make check
make[1]:
gdb 6.8 release
bash-3.2$ uname -a
HP-UX jkhpux1 B.11.11 U 9000/800 1595760578 unlimited-user license
bash-3.2$ gcc -v (still working on getting 4.3.3 to build)
Reading specs from /usr/local/lib/gcc-lib/hppa2.0w-hp-hpux11.11/3.3.6/specs
Configured with: /src/gcc-3.3.6/configure -verbose
---
gdb/doc/gdb.texinfo |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 6aad520..d917523 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -6087,7 +6087,7 @@ Table}.
* OS Information:: Auxiliary
From: Jim Meyering j...@meyering.net
Date: Wed, 11 Feb 2009 09:56:34 +0100
-* Core File Generation::Cause a program dump its core
+* Core File Generation::Cause a program to dump its core
Are you sure this is incorrect English?
Eli Zaretskii e...@gnu.org wrote:
From: Jim Meyering j...@meyering.net
Date: Wed, 11 Feb 2009 09:56:34 +0100
-* Core File Generation::Cause a program dump its core
+* Core File Generation::Cause a program to dump its core
Are you sure this is incorrect English?
Hi Eli,
From: Jim Meyering j...@meyering.net
Cc: bug-gdb@gnu.org
Date: Wed, 11 Feb 2009 21:40:28 +0100
-* Core File Generation::Cause a program dump its core
+* Core File Generation::Make a program dump its core
That sounds much better, thanks.
Hi,
I'm using GDB to debug an application on a remote ARM target, compiled
in Thumb mode (16-bit).
When the size of the locals is too big (apparently something close to
512 bytes), GDB is unable to display the call stack.
See sample code below:
void NoBugStack(void)
{
char buf[508];
Hi,
I'm using MingW GDB 6.8.
I'm debugging 2 DLLs DLL1 and DLL2, which have one source file with the
same name, but different absolute paths; let's say: C:\myProject\dummy.c, and
D:\myProject\dummy.c.
I'm setting a pending breakpoint (i.e. before the DLL is loaded) in
D:\myProject\dummy.c
I am debugging multithreaded executable on Linux. Code is compiled
with g++
gdb is set not to pass SIGINT to executable.
(gdb) info signal
SignalStop Print Pass to program Description
SIGHUPYes Yes Yes Hangup
SIGINTYes Yes No
From: Pedro Alves pe...@codesourcery.com
To: bug-gdb@gnu.org
Sent: Sun, 18 Jan 2009 10:18 am
Subject: Re: 1600 unexpected failures in
gdb-weekly-CVS-6.8.50.20090113.tar.bz2 (on OpenSolaris 2008.11 using
gcc version 4.4.0 20090111)
Did you consider fixing this, and posting a patch at
Using GDB 6.8, GCC 3.4.4, and PowerPC EABI (an embedded system).
When I set a breakpoint on a function that has variable number of
args,
the breakpoint is set on an instruction that is not reached unless a
floating point argument was given.
Ie, with this function:
void VarTest(const char*
-Original Message-
From: Pedro Alves pe...@codesourcery.com
To: bug-gdb@gnu.org
Cc: rob1w...@aol.com
Sent: Sun, 18 Jan 2009 10:18 am
Subject: Re: 1600 unexpected failures in
gdb-weekly-CVS-6.8.50.20090113.tar.bz2 (on OpenSolaris 2008.11 using
gcc version 4.4.0 20090111)
On Sunday 18
I've been trying to debug an mpi program, and I don't have the binding
available for mpi compiled into it, nor can I on my system. I wrote a
client/server perl program to handle this. The program must be
modified to make a system call to start the client (it needs the pid
and mpi id, i couldn't
Did you consider fixing this, and posting a patch at gdb-patches@ ?
Not for a moment. All my spare time is devoted to gcc, OpenSolaris and
a few other things ...
There are other people better qualified than I am to ensure that GDB
and Binutils is fixed _CORRECTLY_ for
the OpenSolaris
On Sunday 18 January 2009 11:25:59, rob1w...@aol.com wrote:
Did you consider fixing this, and posting a patch at gdb-patches@ ?
Not for a moment. All my spare time is devoted to gcc, OpenSolaris and
a few other things ...
There are other people better qualified than I am to ensure that GDB
On Thursday 15 January 2009 13:20:55, rob1w...@aol.com wrote:
While building I found one -Werror:
cc1: warnings being treated as errors
../../gdb-cvs/gdb/procfs.c: In function 'proc_set_watchpoint':
../../gdb-cvs/gdb/procfs.c:2942: error: dereferencing pointer 'pwatch'
does break
[code]
#include iostream
class A
{
public:
A(){}
~A(){std::cout ~A() std::endl;}
};
class B :public A
{
public:
B(){}
~B(){std::cout ~B() std::endl;}
};
main()
{
A a;
B b;
}
[/code]
run output:
# ./a.out
~B()
~A()
~A()
gdb output:
#gdb a.out
(gdb) b A::~A()
Date: Sat, 3 Jan 2009 23:45:20 -0800 (PST)
From: M Jalili work1...@yahoo.com
i compile my c program with gcc 4.3.1 by this command:
gcc -o prog1.out prog1.c -ggdb
then is use gdb to fetch some information in run time.
gdb -e prog1.out -s prog1.out
and when is use info symbol var1 (var1
hi
i compile my c program with gcc 4.3.1 by this command:
gcc -o prog1.out prog1.c -ggdb
then is use gdb to fetch some information in run time.
gdb -e prog1.out -s prog1.out
and when is use info symbol var1 (var1 is a variable)i receve this message:
symbol var1 is a variable with complex or
Hi,
I reported what I thought was a bug in glibc:
http://bugzilla.redhat.com/365111
in which I tried to make gdb simulate a mmap64 failure.
However, using ret (void*)-1 appears not to do what I expected.
In comment #6, Ulrich showed that setting an arch-specific register
did what I wanted:
I am not sure why in one case I am not able to make a target at all
target: ../../common/p1.c
$(CC) -o p1 $
But some how the make command that gets generated is
cc -o p1
the dependency is not working at all. Is there any way to forcefully
do so
is there any way , we can trace how a makefile variable gets its name
Like deep down in a hiearachy of build directories, I find out that
one of the build variables is not what I wanted in the first place. Is
there any way to track , as to who could have changed it
6.8
Hallo Group members
I am working on project where each file is separately compiled then at the end
it is linked to executable.
When I set the breakpoint in some method which is defined outside class body,
but with inline keyword,
I get the following error in gdb:
warning: (Internal error:
Date: Wed, 5 Nov 2008 12:00:54 -0500 From: [EMAIL PROTECTED] Subject:
bug-gdb Digest, Vol 66, Issue 3 To: bug-gdb@gnu.org Send bug-gdb mailing
list submissions to bug-gdb@gnu.org To subscribe or unsubscribe via the
World Wide Web, visit http://lists.gnu.org/mailman/listinfo/bug-gdb or,
Suppose I want to do 1000 nexts
can that be done in one step
___
bug-gdb mailing list
bug-gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gdb
Date: Sat, 1 Nov 2008 13:00:36 -0400 From: [EMAIL PROTECTED] Subject:
bug-gdb Digest, Vol 66, Issue 1 To: bug-gdb@gnu.org Send bug-gdb mailing
list submissions to bug-gdb@gnu.org To subscribe or unsubscribe via the
World Wide Web, visit http://lists.gnu.org/mailman/listinfo/bug-gdb or,
Having no luck getting gdb6.8 to recognize a Solaris gcore(1) generated core
file.
Have the same problem with gdb6.3, and figured I'd give gdb6.8 a try.
BTW, the pstack proc(1) tool and the Solaris modular debugger (mdb)
recognize
a gcore-genrated core dump.
gdb6.8 was built with GCC3.4.6.
...
Date: Fri, 31 Oct 2008 13:00:50 -0400 From: [EMAIL PROTECTED] Subject:
bug-gdb Digest, Vol 65, Issue 1 To: bug-gdb@gnu.org Send bug-gdb mailing
list submissions to bug-gdb@gnu.org To subscribe or unsubscribe via the
World Wide Web, visit http://lists.gnu.org/mailman/listinfo/bug-gdb or,
Hi,
I'm attempting to use GDB on AIX 5.3.0.5 CSP for a multi-threaded application
ported from other *nix platforms
(which is to say the thing works fine on Solaris, centos, HPUX, Linux 2.6, etc).
There are a small number of threads (6 plus one per accepted connection), of
which three
I have a application which is continually coring.
When I examine the core files, the stack looks a little strange.
I see this symbol 0xb5ec6aa0 in ~._86 (this=0xb5bd61e0)
Does anyone know what ~._86 is? It's reported as being in one of my
source files, but it doesn't exist.
Has anyone else seen
Two issues. Both, perhaps, could be argued are IBM's but they are not
likely to change very quickly.
To cut to the chase, I got gdb 6.8 to compile and run on AIX 5.3
(5300-05-CSP-), running gcc 4.3.1 by adding these two lines to be
bottom of my gdb/config.h file:
#define lseek lseek64
Hi,
I just noticed a change between 6.7 and 6.8 in how gdb handles the
implicit type of some large constants. I have the following script:
$ cat gdb-regtest-1
set $foo = (1 46)-1
p/x $foo
file ~/prog/c/misc/sizeof
p/x $foo
set $foo = (1 46)-1
p/x $foo
sizeof is a dummy program which
Hello newsgroup,
I have the following fortran program that I am trying to step through with
gdb. Previously, I have used visual debuggers.
program debug2
USE ISO_C_BINDING, only: C_INT
INTEGER(C_INT) :: I
INTEGER :: J
I = 41
J = 42
PRINT *, I, J
PRINT kind(0), c_int
end program debug1
I want to access the symbol table from within a C program, and gdb
looks like a nice solution. But I couldn't find any api for gdb. Is
there a way to use gdb within C programs ?
___
bug-gdb mailing list
bug-gdb@gnu.org
I put a hardware bp somehwere in my runtime some where.
Now I see that it will delete the breakpoint arbitrarily and go ahead
___
bug-gdb mailing list
bug-gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gdb
Hi,
I need to report a bug. When i copy files through CIFS (1.48aRH) on
Red Hat Enterprise Linux Server release 5.1 (Tikanga) to windows
share, my server crashes. I know that in many old versions, CIFS has the
same problem, but i didn't see this problem reported in this version
(1.48a) of
Building gdb 6.8 on AIX 5.1 using native cc V8.0
Configured as: ./configure, which selected powerpc-ibm-aix5.1.0.0
cc -qversion:
IBM XL C/C++ Enterprise Edition V8.0 for AIX
Version: 08.00..0017
ERRORS:
words.h, line 81.9: 1506-166 (S) Definition of function natural64
requires
gdb still cannot see local variables in a nested C function. This is
reported in PR 1195¹ and 1379².
As the reports are 5 year old by now, I'm wondering whether any work is
being done on this, or if some kind of workaround exists (aside from
avoiding nested functions, not an option in my current
Hi,
I'm using GDB with MinGW on WinXP. I've created a DLL that I'm trying
to debug in GDB. I get an error however when I try to set a
breakpoint ... below is a transcript of the problem. Any ideas how I
can find out more about this Input/Output error I'm having???
Jon
Hi All,
I am facing difficulty in setting break point in a kernel module
which is already loaded. pls share your experiance about this. Do I
need to use attach process? can you give me an idea of how it is
different from debugging a module loaded by gdb.
Cheers,
bijesh
Hi,
I bring the following code in the debugger:
0 //-
1 class F {
2 public:
3 int m_F;
4 //---
5 F(int x) : m_F(x) // constructor
6 { }
7 F(const F f) : m_F(f.m_F) // copy constructor
8 { }
9 };
10
11 int
with aix I am suffering with the problem that it is not ablet o show
me the type of a class or structure of the object that I am working on
Is there any better debuggers for AIX
-Parag
___
bug-gdb mailing list
bug-gdb@gnu.org
Hi,
I'm facing a weird problem with gdb.
Scenario 1 ---
I write a small application which creates a thread and compile it as -
g++ -o thread thread.cpp -pthread
Now I am able to debug the 'thread' application as -
gdb thread
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
after a crash it wont show anything else other than
Cannot access memory at address
___
bug-gdb mailing list
bug-gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gdb
Solaris 9 sparc, gcc 3.4.6, gdb 6.8 compile fails.
./configure and gmake in source directory stops at:
gmake[2]: Entering directory `/stat/src/gdb/gdb-6.8/gdb'
gcc -c -O2 -I. -I.././gdb -I.././gdb/config
-DLOCALEDIR=\/usr/local/share/locale\ -DHAVE_CONFIG_H
-I.././gdb/../include/opcode
Dear Sir
I thing, that I find in new GDB 6.8 new bug.
example :
#include pthread.h
#include stdio.h
#include unistd.h
static pthread_mutex_t mutex;
void* print_pokus(void *unused)
{
while(1)
{
pthread_mutex_lock(amp;mutex);
printf( %s\n, (char *)unused);
I have the following code compiled with gcc 4.1.3 (-g) and run in
gdb 6.6 (debian) (it's similar for stock 6.7 as far as I can tell)
struct Foo {
int x(double d) { return int(d); }
};
int main()
{
Dear Bug-GDB Team,
This got entered into GCC's Bugzilla as Bug 35534. It has been closed, but
you can follow events there.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35534
Having downloaded a CVS snapshot of GDB 6.8 code, there is a coded fix for
the problem in the (static) function
I had host and target (our target arch is mips64octeon, and target os is
2.6.10_mvl401) version gdb both with the same
configuration --target=mips64octeon-montavista-linux.
The mips64_octeon_be-gdb is the host version gdb coming from vender's
cross-compiler toolchain, it is also configured
with
Hi Everyone,
Ilya N. GolubevIlya N. Golubev wrote:
Version: 6.7
Compiler: gcc (GCC) 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)
System: i686-pc-linux-gnu
While compiling the following file, `-Werror' is passed to compiler.
Still
gdb-6.7/bfd/elf32-i386.c: In function `elf_i386_tls_transition':
Hi,
I have a problem when trying to use gdb with a program compiled with
gcc in Cygwin.
I compile this program:
main.c
int main(int argc, char** argv)
{
return 0;
}
/main.c
with this command:
gcc -g main.c
and I get this file:
9757 Mar 1 21:27 a.exe
I then start gdb:
gdb a.exe
On Sat, 2008-02-09 at 13:18 -0800, mearvk wrote:
What files are needed that I don't have? What do I need to do to get
this to compile?
You probably don't have ncurses include files (in the dev package).
Either install them or configure gdb with --disable-tui
--
[]'s
Thiago Jung Bauermann
I get the following data doing a 'make' on a Redhat 2.6.9-55.ELsmp
x86_64 server:
[OUTPUT]
...
In file included from .././gdb/tui/tui-command.c:26:
./tui/tui-data.h:38: error: syntax error before WINDOW
./tui/tui-data.h:50: error: syntax error before '}' token
./tui/tui-data.h:229: error: field
Gdb Crew,
I get this error when attaching to a setuid program that has
_given_up_ its root privilege setuid(getuid()):
-
x~ gdb -p 19484
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
Hi,
compilation does not work with expat-1.95.4,
gcc -c -g -O2-I. -I.././gdb -I.././gdb/config
-DLOCALEDIR=\/usr/share/locale\ -DHAVE_CONFIG_H
-I.././gdb/../include/opcode -I.././gdb/../readline/.. -I../bfd
-I.././gdb/../bfd -I.././gdb/../include -DMI_OUT=1 -DTUI=1 -Wall
Hi,
here is a small program. when, when i am debugging, and analyzing
core it shows me All e replaced by \e Correction, I doubt Not All e,
but some e. here is the sample program and output.
Is this gdb Bug ? on AIX
please note : i am unable to check this on latest version of gdb.
bash-3.00$ cat
Under Debian GNU/Linux unstable, with a Debian
2.6.22-1-686-bigmem kernel, the following program hangs GDB 6.7.1
(as packaged for Debian under Debian version number 6.7.1-1) if
one types control-C to break out to the debugger:
#include pthread.h
#include stdio.h
#include stdlib.h
This comment applies to gdb 6.7 built for an ARM ELF target on both
Linux and Windows(minGW).
Recent GDBs appear to contravene the RSP protocol by issuing the
qSupported command (from remote.c: remote_query_supported( )) before
the channel is initialized by remote_start_remote( ).
The effect is
Hi,
I have cross compiled the gdb-6.3 with arm-none-linux-gnueabi-gcc and cross
compiler has gcc version 4.1.1.
While cross compiling the gdb-6.3, i have faced the tui problem, to
overcome this i have disabled tui (--disable-tui), after this it has
compiled successfully.
I have done the below
How do I get a log of all the functions invoked in a huge C program ?
Does GDB (or ddd) have any such option ?
I mean the simplest possible scenario (please do not go for non-
debuggable object files or other such stuff)
This is required to compare the behaviour of two options which modify
two
RE: Documentation: Debugging with GDB (6.7.5.0)
Hi,
how's it goin'? I'm trying to make a GDB init file work in windows...
In section 2.1.3, regarding .gdbinit, it says that in Windows we should
use the standard name which is .gdbinit (not gdb.ini -- which gdb
actively rejects. Nor gdb.init,
Ted Alves wrote:
RE: Documentation: Debugging with GDB (6.7.5.0)
Hi,
how's it goin'? I'm trying to make a GDB init file work in windows...
In section 2.1.3, regarding .gdbinit, it says that in Windows we should
use the standard name which is .gdbinit (not gdb.ini -- which gdb
actively
Ted Alves [EMAIL PROTECTED] writes:
However, Windows (XP) doesn't allow any file named .anything and
will not accept .gdbinit as a valid file.
If you run gdb from emacs, you may make the .gdbinit from inside emacs
without problems.
Hair is going. Could you pls. advise?
I think this happens
Hello, MR. Key:
I am using the GDB to debug my program.
When I use the command: 'rbreak' to set my breakpoint.
I just try to use only one regular expression to cover all the
possibilities, that is to ignore the case, just like in the vim: to
execute the commad : :set ignorecase
But,
Version: 6.7
Compiler: gcc (GCC) 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)
System: i686-pc-linux-gnu
While compiling the following file, `-Werror' is passed to compiler.
Still
gdb-6.7/bfd/elf32-i386.c: In function `elf_i386_tls_transition':
gdb-6.7/bfd/elf32-i386.c:1174: warning: duplicate
Hi 'body,
i've written a c program which generates children one by one: every
child is generated after the previous is dead.
i launch gdb (6.3.0.0-1.132.EL3rh) and set follow-fork-mode child,
then run the program.
gdb follows the first child, but after it dies, gdb doesn't follow
neither any other
Hi 'body,
i've written a c program which generates children one by one: every
child is generated after the previous is dead.
i launch gdb (6.3.0.0-1.132.EL3rh) and set follow-fork-mode child,
then run the program.
gdb follows the first child, but after it dies, gdb doesn't follow
neither any other
Hi,
I want to know how GDB implements next and step command.
I could not find any document on that.
Is there any documentation available?
Thanks ,
Hemant Shinde
___
bug-gdb mailing list
bug-gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gdb
Hi,
Am interested to debug one shared library using GDB.This shared
libarry is used by a binary (for which i doesn't have the code).I am
aware about at what point of time the library will be called.
Can i debug that library iusing GDB.If yes please let me know the
steps how to proceed further.
Hi,
I am working on extending gdb's printing capabilities and I have noticed that
sometimes the valaddr (+embedded_offset) and address arguments to
val_print get out of sync.
To me it looks like common_val_print should add value_offset(val) to the
result of VALUE_ADDRESS, but I could be wrong.
After switching to x86_64 my gdb otuputs some control characters at
the beggining:
running this:
gdb --batch --quiet --command=/opt/gnome220/share/bug-buddy/gdb-cmd /
opt/gnome220/bin/gcalctool 8028 output.txt
Gives me this:
^[[?1034hUsing host libthread_db library /lib64/libthread_db.so.1.
Hi,
I have a problem opening core file on a different machine from the one
where it is generated.
gdb is not able to open the shared libs although i set GDB_SHLIB_PATH
env varaible.
hpx404!dhirend1:~ [108] gdb /pubhome/ip/iccip/iccip/proj/
golc600_S8P9V64/bin/olcServer
HP gdb 5.7 (Beta) for HP
I had written a command line interface program cli.c.
# useradd -m -G users,wheel -s /home/powah/cli/cli operator
# su - operator
#ps -ef |grep cli
Attach gdb to the cli process id:
#gdb -p pid
Set a breakpoint:
(gdb) b func
(gdb) cont
When the cli function is executed, the func breakpoint is
Hi,
I have a problem when trying to use gdb with a program compiled with
gcc in Cygwin.
I compile this program:
main.c
int main(int argc, char** argv)
{
return 0;
}
/main.c
with this command:
gcc -g main.c
and I get this file:
9757 Jun 24 09:00 a.exe
I then start gdb:
gdb a.exe
gdb endd core.endd-brick-7-1160
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.
Hi,
Since 6.5, I'm having problems with debugging 32bit programs under 64bit gdb on
Solaris 9. It gives a lot of Cannot access memory at address messages where
it's not supposed to. I've checked gdb 6.6 to see if it's any better, but it's
not. So I patched the target.c (all gdb 6.6 now):
Hi again,
I tried to trace how the address gets this value. The address is computed in
findvar.c:495
addr = get_frame_local_address(frame);
addr += SYMBOL_VALUE(var);
For me, get_frame_local_address() returned 0xffbff778 (seems ok), and the
value.ivalue (SYMBOL_VALUE) was 0xffec, so
I am building up GDB (Making) but it fails with message, ada-lex.c missing and
Flex not available.
There are suggestion that I should add ada-lex.c to Makefile.in in gdb but
there is no such a download.
I have installed flex but it does not seem to be recognised.
Where am I going wrong?.
Please
Synopsis :
Gdb failed to stop by Control-C linux on FC5 (2.6.18-1) for multithreaded child
process
Environment :
linux 2.6.17-1.2139 (Fedora core 5).
gdb 6.3 and gdb 6.6
Description :
gdb does not stop on Control C when debugging some processes (apache httpd
child process)
When I try to debug
the recent GDB has problems running GDB `xbacktrace' on EMACS
http://sources.redhat.com/ml/gdb/2007-02/msg00252.html
It seems clear why the change was made:
On the other hand byte arrays become unreadable if printed as strings.
However, it seems that their hope this would not
Hello All,
We did GDB portable for PXE target from the source gdb-5.2.1.
Now we want to do the following two exercises.
*1.**Configure pxe_gdb-5.2.1 for native *
*2.**Configure pxe_gdb-5.2.1 for pxe - gdb-pxe.spec*
For doing *Configure pxe_gdb-5.2.1 for native *
I did the following
Hi folks,
Any body can help me to list the requirements of porting gcc-6.6/GDB to new
target.
Thank you.
~kumar
___
bug-gdb mailing list
bug-gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gdb
Hello folks,
I have just updated my gdb to the version 6.6, provided by SuSE (Suse
Linux 10.1)
Now, wenn I try to debug a staticly linked application, just on the run
comand, I get the error:
gdb appclient-static
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free
Hi folks,
Any body can help me to list the requirements of porting gcc-6.6/GDB to new
target.
Thank you.
~kumar
___
bug-gdb mailing list
bug-gdb@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gdb
For the simple hello world program appended, the command sequence
b main
run
ptype $pc
causes an internal GDB error:
.../gdb/regcache.c:163: internal-error: register_type: Assertion `regnum =
0 regnum descr-nr_cooked_registers' failed.
A problem internal to GDB has been
I'm trying to use remote debugging to debug 64-bit application. It seems
not working. I even tried to do it on the same machine - the same
result.
Looks like 64-bit register value is not handled properly.
Here are the details:
GDB client console:
(gdb) target remote :1234
Remote debugging
Hi,
I am meeting a problem that orig_r0 is overwritten by gdbserver(gdb 6.3)
on ARM.
It is because store_register/store_regs (in arm-linux-nat.c) set
register with ptrace(PTRACE_SETREGS ...)
But as orig_r0 is not mapped by gdbserver, it will be overwritten.
This lost of orig_r0 will prevent
201 - 300 of 5286 matches
Mail list logo
