Dear Brian,
it is hard to admit, but you are right even if a structure was not directly
involved. The corresponding high level statements were
double guarded_log( double *arg ) {
try {
return log( *arg ); // e.g. arg==0 or arg==0x1234.
} catch ( s2e::SCN(SIGSGEV)*e ) {
Hugo Mildenberger wrote:
>
> Dear friends,
>
> I'm working on a library, which is able to map (at least synchronous) kernel
> signals to c++ exceptions in a way, that c++ exception handlers can
> determine reason and location of failure in a very detailed manner. Within
> that context, I detecte
Dear friends,
I'm working on a library, which is able to map (at least synchronous) kernel
signals to c++ exceptions in a way, that c++ exception handlers can
determine reason and location of failure in a very detailed manner. Within
that context, I detected a surprising difference in the behavio
3 matches
Mail list logo
