filename_cmp.c

Hi !

I am used arm-elf-gdb & keil toolchain & have more problems in sets breakpoints in Eclipse IDE on Windows
platform. After modify file filename_cmp.c, it's been absent (sorry for my english).
Source code, written by me:

filename_cmp.c:

#ifdef HAVE_CONFIG_H
#include "config.h"
#endif

#ifdef HAVE_STRING_H
#include <string.h>
#endif

#include "filenames.h"
#include "safe-ctype.h"
#include <alloca-conf.h>

/* #define LOC_DEBUG */

void correct_name(char * s, int len)
{
    char * p = s, * plast = s;

    for (;;)
    {
        if (p[2] == '\\')
            p[2] = '/';

gdb bug on AIX 5.3 64bit

 Hi.

I have a problem in use gdb

*- env*
 AIX 5.3 64bit
 IBM XL C/C++ Enterprise Edition for AIX, V9.0.
 gdb version 7.1
 export OBJECT_MODE=64
 export CC=xlc
 export CFLAGS="-g -q64"

*- solved some problem*

  1. compile...
  "rs6000-core.c", line 114.10: 1506-007 (S) "struct core_dump" is
undefined.
  "rs6000-core.c", line 127.10: 1506-007 (S) "struct vm_info" is undefined.
  < my action > remove option at 'bfd/Makefile' file : remove that
'-DAIX_CORE' (2 count)

  2. compile...
  xlc -c -g -q64 -DDEFAULT_INLINE=PSIM_INLINE_LOCALS    
-DWITH_HOST_BYTE_ORDER=BIG_ENDIAN -DWITH_SMP=5             
-DHAVE_TERMIO_STRUCTURE -DHAVE_TERMIO_CLINE -DHAVE_DEVZERO     -I. -I.
-I./../../include -I../../bfd -I./../../bfd -I../../gdb -I./../../gdb 
-I./../../gdb/config -I../../intl -DHAVE_COMMON_FPU -I../common
-I./../common debug.c
  "words.h", line 81.9: 1506-166 (S) Definition of function natural64
requires parentheses.

GDB documentation: info format

Hello,

I am currently trying to include GDB documentation into gNewSense  
distribution, in info format. While most of GNU software documentation  
is available directly from GNU site in info format (see  
http://www.gnu.org/manual/manual.html), I'm surprised to see this is  
not the case for GDB. I would like to know if you could make info  
documentation for GDB available on your website. If not, could you  
please tell me how I can build it.

Thanks,

Christophe

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

how to use gdb with inputfile

Hi there,

How can I use gdb to debug   ./foo < foo.iniput? 

Thanks,
Bob
--

-- 
View this message in context: http://old.nabble.com/how-to-use-gdb-with-inputfile-tp28276878p28276878.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

Re: how to use gdb with inputfile

On Sunday 18 April 2010 03:33:59 Bob WM wrote:
> Hi there,
>
> How can I use gdb to debug   ./foo < foo.iniput?
>
> Thanks,
> Bob

Bob

I don't know how to do this directly but there is a brute force way to do this 
using gdb attach.

Change your main with

volatile int spinning=1;

main()
{
  while(spinning){}
...
}

Now you can launch

$ ./foo <foo_input

which will get stuck in the infinite loop

From a separate terminal

info

How gdb accesses another process variable

Hi,

I see the feature provided by gdb, that we can set a variable (using set
command) for a running process
through gdb. Can any one tell me how can gdb (as a process) could access the
variables of other process.
I guess its more of a OS related doubt. Please let me know. Thanks.
--

-- 
View this message in context: http://old.nabble.com/How-gdb-accesses-another-process-variable-tp28287751p28287751.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

Re: How gdb accesses another process variable

On Tuesday 20 April 2010 08:49:59 CygwinUser wrote:
> Hi,
>
> I see the feature provided by gdb, that we can set a variable (using set
> command) for a running process
> through gdb. Can any one tell me how can gdb (as a process) could access
> the variables of other process.
> I guess its more of a OS related doubt. Please let me know. Thanks.

You can do this in *nix (Linux etc) and I guess cygwin too through the attach 
command.

The gdb attach command lets you attach to a running process.

eg.

Start  ./foo running in one terminal.

In another terminal
$ ps -ef
note down process number of the process you want. Let's say 12345.
$ gdb ./foo
(gdb) attach 12345
(gdb) 
at this point  you have attached to the process and stopped it and can debug, 
single step etc just like any other debugged process.
Let's set var to 10.
(gdb) p var=10
You can then detach from the process with
(gdb) detach

GDB-Problem (debuginfo)

You must  add the community repository labeled DEBUG in yast.
cf  http://forums.opensuse.org/get-help-here/applications/427318-missing-
separate-debuginfo.html

I'm currently having the same problem, except I can't find all debuginfo 
packages.

Re: How gdb accesses another process variable