Re: debugging gnulib on Os/2

[Bruno Haible]

[Elbert, *please* keep bug-gnulib in CC. Your refusal to do so wastes my time
with mail management: First, I have to forward your mail to the list. Then
since I reply to the forwarded mail I cannot use the mailer's normal "Reply"
feature and have to indent each line one by one. And then the automatic
grouping of related mails in the mailer does not work, so I have to do manual
triage. This is very annoying!!]

Elbert Pol wrote:
> Where to get that patch?

You can download a tarball for testing from
  http://www.haible.de/bruno/gnu/testdir-stdioext.tar.gz
It was generated from today's gnulib using
  $ ./gnulib-tool --create-testdir --dir=/dev/shm/testdir-stdioext --with-tests 
fbufmode fflush fpending fpurge freadable freadahead freading freadptr 
freadseek fseek fseeko fseterr ftell ftello fwritable fwriting

> And should i use it ?

./configure CFLAGS=-g
make
make check

and please report the results.

> And i never did use a debugger so give me please some backup about how 
> to run ...

Debugging with gdb generally goes like this:
  - You compile with debugging information (that's what you CFLAGS=-g above
    is for).
  - Run gdb on the program:
    $ gdb test-fflush
  - Inside gdb, control the program:
    (gdb) help
    (gdb) run
    (gdb) where
    (gdb) info locals
Try debugging a simple hello-world program first, to get familiar with
breakpoints and single-stepping.

Bruno