zerobugs Google Group

Re: Execute zero with a program, but without running it as soon as zero starts up

2008-07-10T06:19:15Z

Hi Ary,
Try defining ZERO_START_MAIN to 0 or "false" in your environment. The
program should load and stop at the first instruction. See also:
[link]
As a side comment: my understanding is that Eclipse interfaces with GDB
using DMI (debugger-machine interface, [link]).

Execute zero with a program, but without running it as soon as zero starts up

2008-07-09T15:28:42Z

Hi,

I'm developing a user interface for ZeroBUGS for Descent (
[link] ). I'm already supporting gdb and
ddbg. With all of them what I do is the following:
1. run the debugger, telling it which program I'll be debugging
2. set the breakpoints the user indicated
3. run the debugged program (the debugee)

new website

2008-06-03T16:19:02Z

Hi,

The ZeroBUGS website will launch at the end of this week in a new,
revamped layout.
Take a peek at the new site design here:
[link]

Enjoy!
Cristian

Re: Gnu C++ compiler compatibility

2008-04-11T17:14:06Z

Yes, the debugger supports multi-threaded applications.
Which specific version of RedHat are you interested in running on?
There are pre-compiled versions for Fedora 7 and 8 and Centos (which is a
community-developed clone of RedHat Enterprise) available for download here:
[link]. It is not the most up-to-date code,

Gnu C++ compiler compatibility

2008-04-10T17:57:03Z

Can this debugger be used to debug mulithreaded programs compiled with
GNU C++ compiler under Red Hat Linux? Can I use X to run to display
the debugger GUI on my Windows PC?

Re: Fedora 8 x86_64

2008-03-31T14:57:25Z

Thanks by the way...
--
Orhun Birsoy

Re: Fedora 8 x86_64

2008-03-31T14:43:05Z

Yes, I am experimenting with them.

Re: Fedora 8 x86_64

2008-03-31T06:12:08Z

I will add it to my backlog.
Are you using any of the C++0x features in GCC 4.3?

Fedora 8 x86_64

2008-03-31T01:31:50Z

hi,

Is there any change to have a x86_64 bit build for Fedora 8?

Thanks...

note: I am also using gcc 4.3. Hopefully it won't cause any problems.

Re: D: function names in stack trace window should be demangled

2008-03-18T01:38:03Z

You need to set ZERO_D_SUPPORT=true or ZERO_D_SUPPORT=1 in your
environment.

Re: debug info packages for F8 & libc

2008-03-14T06:36:29Z

For the benefit of other users reading this thread:

After working on this issue off line with gshcherb I found a bug in
the ZeroBUGS plugin that deals with DWARF debug information;

the bug was since fixed in builds for Ubuntu (i386, x86_64), and
Fedora 7 and 8 (i386).

Cristian

Re: D: function names in stack trace window should be demangled

2008-03-09T07:25:38Z

No I cannot use std.demangle, for the following reasons:
1) the inter-operation between C++ (the language zero is written in) and D
is great with D 2.0, but sucks really bad in 1.x; D 2.0 is still a moving
target as a language and I am not sure that I want to commit to using it
(yet);
2) DMD is a 32-bit compiler only, so std.demangle would not help me much on

D: function names in stack trace window should be demangled

2008-03-09T06:26:57Z

You can use D module std.demangle.

Re: C++ exceptions

2008-03-07T06:54:53Z

Wow, that was fast! I've just checked it and it really does work.

Re: C++ exceptions

2008-03-07T01:56:49Z

I have implemented the "stop at B" behavior, which works when "Break
At Exceptions" is NOT set (otherwise the debugger stops on each
throw). This is an improvement IMO over the initial behavior, thanks
for suggesting it. If you want to try it out, the Gutsy and Fedora 8
builds available on the download page sport the feature.