OK, but why do not add the debug info in an external file (conform to
stabs/dwarf specification)?
I don't understand why debug info should be a big problem. If you don't
want it, strip does the job very well. It's just one command away. And
you don't need to do it every time you compile your a
Hi,
OK I understand but why do not add a new option to avoid the store of the
debug info on the final compiled file (or generated ppu files)?
Currently I must always use "strip" and I cannot use it on "ppu" files?
2008/1/13, Bee <[EMAIL PROTECTED]>:
>
> > OK, but why do not add the debug info
Fabio Dell'Aria schreef:
Hi,
OK I understand but why do not add a new option to avoid the store of
the debug info on the final compiled file (or generated ppu files)?
That option is -Xs. Don't use it in combination with -gl because that
adds the debug info again.
Currently I must always
> Fabio Dell'Aria schreef:
>> Hi,
>>
>> OK I understand but why do not add a new option to avoid the store of
>> the debug info on the final compiled file (or generated ppu files)?
>>
>
> That option is -Xs. Don't use it in combination with -gl because that
> adds the debug info again.
-Xg will ge
Op zaterdag 12-01-2008 om 20:11 uur [tijdzone +0100], schreef Bogusław
Brandys:
> Jonas Maebe wrote:
> >
> > On 12 Jan 2008, at 16:07, Bogusław Brandys wrote:
> >
> >> Could we have debug info as separate file ? If this would be possible
> >> I could create release stripped EXE and yet be able t
Op Sun, 13 Jan 2008, schreef Joost van der Sluis:
Op zaterdag 12-01-2008 om 20:11 uur [tijdzone +0100], schreef Bogus?aw
Brandys:
Jonas Maebe wrote:
You can already do this: compile a "release executable" with debug info,
and then distribute a stripped copy of that executable. The addresses
Daniël Mantione wrote:
Op Sun, 13 Jan 2008, schreef Joost van der Sluis:
Op zaterdag 12-01-2008 om 20:11 uur [tijdzone +0100], schreef Bogus?aw
Brandys:
Jonas Maebe wrote:
You can already do this: compile a "release executable" with debug
info,
and then distribute a stripped copy of that
Fabio Dell'Aria wrote:
Can you tell we more about the iirc gdb please?
IIRC -> If I Recall Correctly
This is about plain gdb, since fpide uses gdblib I don't know if it
counts foir that too.
Anyway, on my fedora core, I've the option to install a
somelib-debuginfo package. This package ins
Op Sun, 13 Jan 2008, schreef Marc Weustink:
Fabio Dell'Aria wrote:
Can you tell we more about the iirc gdb please?
IIRC -> If I Recall Correctly
This is about plain gdb, since fpide uses gdblib I don't know if it counts
foir that too.
Anyway, on my fedora core, I've the option to instal
I haven't tested this, but from what I read, if strip can preserve the
symbols in a separate file then gdb should be able to load them.
http://www.delorie.com/gnu/docs/gdb/gdb_125.html
|exec-file [ filename ]|
Specify that the program to be run (but not the symbol table) is
found in fil
sorry my mailer wrapped that a bit awkward. the important part was:
|symbol-file [ filename ]|
Read symbol table information from file filename. |PATH| is
searched when necessary. Use the |file| command to get both symbol
table and program to run from the same file.
Martin Friebe
Op zondag 13-01-2008 om 17:48 uur [tijdzone +0100], schreef Daniël
Mantione:
>
> Op Sun, 13 Jan 2008, schreef Joost van der Sluis:
>
> > Op zaterdag 12-01-2008 om 20:11 uur [tijdzone +0100], schreef Bogus?aw
> > Brandys:
> >> Jonas Maebe wrote:
> >>>
> >>> You can already do this: compile a "rele
Op zondag 13-01-2008 om 19:09 uur [tijdzone +0100], schreef Daniël
Mantione:
>
> Op Sun, 13 Jan 2008, schreef Marc Weustink:
>
> > Fabio Dell'Aria wrote:
> >> Can you tell we more about the iirc gdb please?
> >
> > IIRC -> If I Recall Correctly
> >
> > This is about plain gdb, since fpide uses gd
13 matches
Mail list logo
