think of anything anymore short of compiling xxgdb from
> source and debugging it under gdb.
I'll try that...
> I would be interested to know why people still use xxgdb now that
> DDD is stable though; if there are good reasons (rather than old
> habits dying hard), it makes sens
On Thu, 11 Nov 1999, J.H.M. Dassen (Ray) wrote:
[ snip ]
: In my GECOS field it has no quotes or backslashes; I still haven't figured
: out what is adding them (probably my MTA).
The MTA is adding quotes to protect the parentheses; the wuotes are then
escpaed by backslashes.
Lose the parenthe
On Thu, Nov 11, 1999 at 11:20:28 -0800, J C Lawrence wrote:
> Unfortunately I can't let you onto the machine in question (behind a
> firewall). Is there any data I could provide that might be useful?
I can't think of anything anymore short of compiling xxgdb from source and
de
On Thu, 11 Nov 1999 18:17:20 +0100
Ray <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 10, 1999 at 13:03:56 -0800, J C Lawrence wrote:
>> I'm running a straight Debian potato system. Everything is up to
>> date. gdb works just fine. xxgdb returns the following, al
On Wed, Nov 10, 1999 at 13:03:56 -0800, J C Lawrence wrote:
> I'm running a straight Debian potato system. Everything is up to
> date. gdb works just fine. xxgdb returns the following, always:
>
> Error: Cannot perform malloc
That's bug #47452 (http://www.debian.org
I'm running a straight Debian potato system. Everything is up to
date. gdb works just fine. xxgdb returns the following, always:
Error: Cannot perform malloc
Ideas?
--
J C Lawrence Internet: [EMAIL PROTECTED]
--(*)Int
On Mon, Apr 19, 1999 at 15:23:32 -0700, Micha Feigin wrote:
> I am trying to run a debuger under x for c / c++ when i try to run ddd i
> get a reply:
> ddd: Symbol 'XmStrings' hasdifferent size in shared object, consider
> relinking
This means that the DDD binary you're using was linked against a
unning DDD version 3.1.3 (I think potato) on a mostly slink
machine (gdb and g++, gcc are from potato).
g++ and gcc i need the new ones because some program demands it for
compilation. The dubugers i updated for some reson with them. If it
will solve the problem i can downgrade.
Also from xxgdb I get
Hi,
When I try to debug an app, which does use some shared libraries, with
ddd/gdb/xxgdb the gdb segfault's when it's launched by the gdb
frontends.
When launched from DDD, a dialog pops up saying "GDB could not be
started.", and gives the "Exit", "Help" a
Hi All,
I've just installed Debian 1.3.1 on my computer.
Every time I try to use xxgdb and type a command (like "file xxx"), it
stats beeping and writing lots of error messages.
Gdb is working fine.
Thanks,
Fernando Pinho
Hi All,
I've just installed Debian 1.3.1 on my computer.
Every time I try to use xxgdb and type a command (like "file xxx"), it
stats beeping and writing lots of error messages.
Gdb is working fine.
Thanks,
Fernando Pinho
>
> Thank you for your reply:
>
> Firstly, at the command line I enter the following --> xxgdb gdbtst
> Following that, the 4 windows open and then close. In the window
> where I started the program I get Segmentation Violation. So I don't have
> an opportunity to do
Thank you for your reply:
Firstly, at the command line I enter the following --> xxgdb gdbtst
Following that, the 4 windows open and then close. In the window
where I started the program I get Segmentation Violation. So I don't have
an opportunity to do anything within the debugger.
I
>
> Hello all:
>
> I'm trying to use xxgdb or ddd to debug a small program.
> With xxgdb when I attempt to load a program (compiled
> with the -g option) I get a segmentation fault. When I try
> to use ddd, I get can't malloc.
>
> I there something other th
Hello all:
I'm trying to use xxgdb or ddd to debug a small program.
With xxgdb when I attempt to load a program (compiled
with the -g option) I get a segmentation fault. When I try
to use ddd, I get can't malloc.
I there something other than the -g option I must use ?
Peter
15 matches
Mail list logo
