Need help

Lowyat.NET Lowyat.NET Rules and Regulations

FAQ Help Search Members Calendar

Outline · [ Standard ] · Linear+

Need help, WHAT AND WHICH

Share on

| Track this topic | Email this topic | Print this topic

lhscindy

Jun 13 2006, 08:28 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #1

Getting Started

Group: Junior Member
Posts: 100
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Jan 2003

I hav to build a program to detect bug.
What should i do....
Which to use... C or C++ or Visual Basic....
Any suggestion....

TQ

natakaasd

Jun 13 2006, 08:32 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #2

Look at all my stars!!

Group: Senior Member
Posts: 2,180
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Nov 2005

which is the programming language u r more familiar with...?

yingchai

Jun 13 2006, 08:44 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #3

~extraordinaire~

Group: Senior Member
Posts: 1,061
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Jul 2005
From: KL

depends on which platform u going 2 use the debugger...

if ur debugger is used in windows, then can use maybe asp.net or C#

if in linux platform, c++ is more preferable...

lhscindy

Jun 13 2006, 08:46 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #4

Getting Started

Group: Junior Member
Posts: 100
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Jan 2003

I am more familiar with c and java but my fren say if use visual basic is easier

lhscindy

Jun 13 2006, 08:50 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #5

Getting Started

Group: Junior Member
Posts: 100
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Jan 2003

actually i want to know how to find bug.....
i dun understand....

nxfx

Jun 14 2006, 09:21 AM

Show posts by this member only |This post's rating (0+, 0-) | Post #6

Enthusiast

Group: Senior Member
Posts: 828
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Jan 2003

I dun understand your question also. What you mean by finding bug? You want to build a debugger? Please give an example.

lhscindy

Jun 14 2006, 07:54 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #7

Getting Started

Group: Junior Member
Posts: 100
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Jan 2003

build a debugger lor...

anthony_yio

Jun 14 2006, 08:35 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #8

........

Codemasters

Group: Elite
Posts: 1,794
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Jan 2003

QUOTE(lhscindy @ Jun 14 2006, 07:54 PM)

build a debugger lor...

B4 you even start. Do you know how to operate a debugger?

natakaasd

Jun 14 2006, 08:52 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #9

Look at all my stars!!

Group: Senior Member
Posts: 2,180
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Nov 2005

debugger using VB? might be possible and simpler, but then again, what laguage are you going to debug...?

lhscindy

Jun 16 2006, 04:18 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #10

Getting Started

Group: Junior Member
Posts: 100
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Jan 2003

B4 you even start. Do you know how to operate a debugger?

I really dun no how a debugger works. That y i wan to ask.....

randytsx

Jun 17 2006, 07:10 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #11

Getting Started

Group: Junior Member
Posts: 162
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Dec 2005
From: The other side of the gate.

so u dun know how to operate a debugger?

I'm not an expert programmer but i think that debugger is that thing that shows u the errors on which line right? most of them can point u directly to that line containing the error and highlight the error part of the code at that line.....

EDIT: it also tells u a thing or two about the error....but if the code is too complex, sometimes the debugger might only help juz a little.....

This post has been edited by randytsx: Jun 17 2006, 07:12 PM

asc2

Jun 17 2006, 07:16 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #12

Casual

Group: Junior Member
Posts: 311
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Jan 2003

QUOTE(randytsx @ Jun 17 2006, 07:10 PM)

so u dun know how to operate a debugger?

I'm not an expert programmer but i think that debugger is that thing that shows u the errors on which line right? most of them can point u directly to that line containing the error and highlight the error part of the code at that line.....

EDIT: it also tells u a thing or two about the error....but if the code is too complex, sometimes the debugger might only help juz a little.....

ermm i think that is for vb

debugger - something you can use to break at a certain point in your program and observe the behaviour of the program, like to watch the value of variables at runtime, step thru your code can give you a picture of the flow of the program

sunsuron

Jun 17 2006, 10:28 PM

Show posts by this member only |This post's rating (0+, 0-) | Post #13

PHP Web Developer

Group: Senior Member
Posts: 750
Ratings earned: 0+, 0-
Ratings given: 0+, 0-

Joined: Nov 2004

If you never use debugger before, you should spend some times before creating one.

A debugger helps us understand what is really going on when our program is running. It is the x-ray of software development, allowing us to see inside programs and diagnose potential problems.

Without a debugger we are guessing; with a debugger we are seeing. It is as simple as that. Whatever time we invest in learning to use any debugger is time well spent.

A debugger is also a powerful tool for understanding code written by others. By putting someone else's code into the debugger and stepping through it, we can see exactly how the methods work and what data they manipulate.

For example setting a breakpoint. A breakpoint is an instruction to the debugger to stop running. We set a breakpoint and then run the program and the debugger runs the program up until the breakpoint. Then we have the opportunity to examine the value of our variables at this point in the execution. Examining our program as it runs can help us untangle otherwise impenetrable problems.

Having said that, our debugger should have a breakpoint window or watch window that enables us to expand variables when examining values such as the autos and locals windows or the call window stack in visual studio.

This post has been edited by sunsuron: Jun 17 2006, 10:30 PM

« Next Oldest · Codemasters · Next Newest »