As you can see, the patch is trivial, so I have no clue why this wasn't
left alone when they modified symfile.c. If I can be bothered I'll
submit it to them.
Hmm. Looking at this patch, it seems it's complaining about being
handed a hex value where it's looking for an address. I'd
I'm using a derivative of the .gdbinit.vinum files that is available in
the modules/vinum directory. For them to work the following patch is
needed in gdb52.
As you can see, the patch is trivial, so I have no clue why this wasn't
left alone when they modified symfile.c. If I can be bothered
On Tue, May 28, 2002 at 03:54:21PM +0200, Nick Hibma wrote:
I'm using a derivative of the .gdbinit.vinum files that is available in
the modules/vinum directory. For them to work the following patch is
needed in gdb52.
As you can see, the patch is trivial, so I have no clue why this wasn't
Doh! me bad, I didn't include an example:
The attached .gdbinit loads the symbols from a module, but needs the
start address of the .text section.
add-symbol-file filename address
address cannot be an expression in gdb5.2, just a simple address
('0x[0-9a-f]+' or '[0-9]+').
Nick
On
On Tuesday, 28 May 2002 at 15:54:21 +0200, Nick Hibma wrote:
I'm using a derivative of the .gdbinit.vinum files that is available in
the modules/vinum directory. For them to work the following patch is
needed in gdb52.
As you can see, the patch is trivial, so I have no clue why this wasn't
