signal.h

[David Willoughby]

I'm attempting to catch bugs in my program using signal.h with sigsegv.
now i know when i'm in gdb i can catch bugs but is there any variable
that stores like the file that caused the bug and possible calling
procs? or would that only be left to something with gdb.

[Ian Collins]

David Willoughby wrote:

I'm attempting to catch bugs in my program using signal.h with sigsegv.
now i know when i'm in gdb i can catch bugs but is there any variable
that stores like the file that caused the bug and possible calling
procs? or would that only be left to something with gdb.

You'd better ask in a group or forum dedicated to your platform and
tools. When you, quote an example.

--
Ian Collins.

[santosh]

David Willoughby wrote:

I'm attempting to catch bugs in my program using signal.h with sigsegv.
now i know when i'm in gdb i can catch bugs but is there any variable
that stores like the file that caused the bug and possible calling
procs? or would that only be left to something with gdb.

The standard macros __FILE__ and __LINE__ may do what you want. For
more you'll have to use implementation specific extensions.

[jaysome]

On 8 Dec 2006 22:13:36 -0800, "santosh" <sa*********@gmail.comwrote:

>David Willoughby wrote:

>I'm attempting to catch bugs in my program using signal.h with sigsegv.
now i know when i'm in gdb i can catch bugs but is there any variable
that stores like the file that caused the bug and possible calling
procs? or would that only be left to something with gdb.

The standard macros __FILE__ and __LINE__ may do what you want. For
more you'll have to use implementation specific extensions.

I can't think of any way the standard macros __FILE__ and __LINE__
could help in the general case of a SIGSEGV signal.

Moreover, saying that "implementation-specific extensions" could help
in the general case implies to me *compiler* implementation-specific
extensions. But more likely than not, it's things like debuggers,
which are beyond the scope of the ANSI/ISO C standard--which is what
we discuss here--that will help the OP.

I think the spirit of your post was that the OP should look for help
in another, more appropriate newsgroup. If so, indeed the OP should
(and find out, that, that would only be left to something with gdb, as
the OP surmised :^).

Best regards
--
jay

[CBFalconer]

jaysome wrote:

"santosh" <sa*********@gmail.comwrote:

>David Willoughby wrote:

>>I'm attempting to catch bugs in my program using signal.h with
sigsegv. now i know when i'm in gdb i can catch bugs but is there
any variable that stores like the file that caused the bug and
possible calling procs? or would that only be left to something
with gdb.

The standard macros __FILE__ and __LINE__ may do what you want. For
more you'll have to use implementation specific extensions.

I can't think of any way the standard macros __FILE__ and __LINE__
could help in the general case of a SIGSEGV signal.

Moreover, saying that "implementation-specific extensions" could help
in the general case implies to me *compiler* implementation-specific
extensions. But more likely than not, it's things like debuggers,
which are beyond the scope of the ANSI/ISO C standard--which is what
we discuss here--that will help the OP.

I think the spirit of your post was that the OP should look for help
in another, more appropriate newsgroup. If so, indeed the OP should
(and find out, that, that would only be left to something with gdb, as
the OP surmised :^).

Before calling the function that signals SIGSEGV he can emit a
message formed from the __FILE__ and __LINE__ macros. Something
like:

if (evilcondition) {
printf("Fault in %s line #%s\n", __FILE__, __LINE__);
signal(....);
}

--
Chuck F (cbfalconer at maineline dot net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net>

[Keith Thompson]

CBFalconer <cb********@yahoo.comwrites:
[...]

Before calling the function that signals SIGSEGV he can emit a
message formed from the __FILE__ and __LINE__ macros. Something
like:

if (evilcondition) {
printf("Fault in %s line #%s\n", __FILE__, __LINE__);
signal(....);
}

I'd add a call to fflush(stdout) after the printf.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.