Debugger not reaching the first line of code

[shishir]

hi,
I was asked this peculiar question in an interview - There's a one line
C code ( the simplest you can assume , a printf statement inside the
main) and a breakpoint has been set at that very first line. The code
compiles and runs but the debugger never reaches that breakpoint. What
could be the possible reason/bug/issue behind this. Does anyone have
any clue to this.
Thanks,
Shishir

 

[Ben C]

hi,
I was asked this peculiar question in an interview - There's a one line
C code ( the simplest you can assume , a printf statement inside the
main) and a breakpoint has been set at that very first line. The code
compiles and runs but the debugger never reaches that breakpoint. What
could be the possible reason/bug/issue behind this. Does anyone have
any clue to this.
Thanks,

An undefined global initializer, maybe?

 

[=?ISO-8859-1?Q?=22Nils_O=2E_Sel=E5sdal=22?=]

hi,
I was asked this peculiar question in an interview - There's a one line
C code ( the simplest you can assume , a printf statement inside the
main) and a breakpoint has been set at that very first line. The code
compiles and runs but the debugger never reaches that breakpoint. What
could be the possible reason/bug/issue behind this. Does anyone have
any clue to this.

Could be a user bug.


Provide more info directed in the proper channel for your particular
platform/compiler/debugger for more answers.

 

[Richard Bos]

I was asked this peculiar question in an interview - There's a one line
C code ( the simplest you can assume , a printf statement inside the
main) and a breakpoint has been set at that very first line. The code
compiles and runs but the debugger never reaches that breakpoint. What
could be the possible reason/bug/issue behind this. Does anyone have
any clue to this.

Clearly the interviewer had read the FAQ, and you haven't.

HTH; HAND.

Richard

 

[Chang Feng]

Where can I find the FAQ?
Thanks!

Clearly the interviewer had read the FAQ, and you haven't.

HTH; HAND.

Richard

 

[Keith Thompson]

Where can I find the FAQ?
Thanks!

A Google search for "comp.lang.c FAQ" or "C FAQ" would have found
<http://www.c-faq.com/>.

Please also read <http://www.caliburn.nl/topposting.html> and
<http://clc-wiki.net/wiki/Introduction_to_comp.lang.c>.

 

[Richard G. Riley]

Clearly the interviewer had read the FAQ, and you haven't.

HTH; HAND.

Richard

Great "advice". And would be much more helpful had you provided a link or an
excerpt from the FAQ to help. Or was your only reason to reply to
belittle the OP who may, or may not, have been aware of the FAQ?

To the OP : dig around here if you have web access - http://c-faq.com/

In addition, what is HTH and HAND? I thought acronyms were frowned
upon here?

 

[pete]

To the OP

ITYM Original Poster

I thought acronyms were frowned upon here?

It looks like you didn't.

 

[Richard G. Riley]

ITYM Original Poster


It looks like you didn't.

Fair point ... ( I didnt know an acronym for that...).

 

[Mark McIntyre]

Great "advice". And would be much more helpful had you provided a link or an
excerpt from the FAQ to help.

About every fourth post here, not to mention the regular 'welcome'
message, mentions it. And frankly anyone who can't use google is
probably not going to make a programmer anyway.

In addition, what is HTH and HAND? I thought acronyms were frowned
upon here?

What on earth gave you that idea?
Mark McIntyre

 

[Mark McIntyre]

Fair point ... ( I didnt know an acronym for that...).

YGMBTRG.

Mark McIntyre

 

[CBFalconer]

.... snip ...

About every fourth post here, not to mention the regular 'welcome'
message, mentions it. And frankly anyone who can't use google is
probably not going to make a programmer anyway.


What on earth gave you that idea?

The fact that we usually yell at imbeciles who insist on using
confusing and silly abbreviations such as 'u', 'ur' and 'plz'.
Acronyms are also pretty silly when their primary purpose is to
confuse the reader. Maybe you should join the Fraternal Order of
Programmers Accustomed to Clarity in Code and Prose. FOPACCAP.

Hope That Helps. Have A Nice Day.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>

 

[Skarmander]

The fact that we usually yell at imbeciles who insist on using
confusing and silly abbreviations such as 'u', 'ur' and 'plz'.
Acronyms are also pretty silly when their primary purpose is to
confuse the reader. Maybe you should join the Fraternal Order of
Programmers Accustomed to Clarity in Code and Prose. FOPACCAP.

Hope That Helps. Have A Nice Day.

"HTH. HAND." is an idiom. I doubt you could call its primary purpose
confusion. It may not be readily understood in all cases, but in this case
the speaker clearly expected it to be, if perhaps not necessarily by the
addressee.

The situation for "u", "ur" and "plz" is similar, except that in these cases
the idioms are considered a mark of unprofessionality and/or immaturity.
That their meaning is readily accessible even to the unfamiliar is not
disputed by anyone. Of course, this entire discussion itself is a rather
immature clash of egos with no real goal of a productive consensus, but as
they say, "YMMV".

What would Usenet come to if you could no longer use such eloquent
expressions as "TANSTAAFL" and "YKYBHTLW"? That they are unfamiliar to some
should not hold us back; the acronym dictionaries are only a few lookups away.

S.

 

[Walter Roberson]

"HTH. HAND." is an idiom. I doubt you could call its primary purpose
confusion. It may not be readily understood in all cases, but in this case
the speaker clearly expected it to be, if perhaps not necessarily by the
addressee.

The situation for "u", "ur" and "plz" is similar, except that in these cases
the idioms are considered a mark of unprofessionality and/or immaturity.

*personally*, I consider "HTH. HAND." to -usually- be marks of
unprofessionality and/or immaturity, as they are often written in
contexts where they would likely be interpreted as being dismissive.

 

[CBFalconer]

.... snip ...

The situation for "u", "ur" and "plz" is similar, except that in
these cases the idioms are considered a mark of unprofessionality
and/or immaturity. That their meaning is readily accessible even
to the unfamiliar is not disputed by anyone. Of course, this
entire discussion itself is a rather immature clash of egos with
no real goal of a productive consensus, but as they say, "YMMV".

No, they are not similar. They depend on prononciation, and many
participants here have only some writing contact with English, so
prononciation is meaningless to them, and the abbreviations are
meaningless. Besides marking the user as immature they also show
him/her to be careless and imprecise.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>

 

[Richard Bos]

Hope That Helps. Have A Nice Day.

Not necessarily in the case Mr. Riley refers to.

HTH - HAND!

Richard

 

[Mark McIntyre]

The fact that we usually yell at imbeciles who insist on using
confusing and silly abbreviations such as 'u', 'ur' and 'plz'.

Those aren't acronyms.

Acronyms are also pretty silly when their primary purpose is to
confuse the reader.

TAANSTAFL.


Mark McIntyre