Fix bugs in NgSendMsg() and NgSendAsciiMsg() where the wrong token
value could be returned when the debug level was non-zero. Submitted by: Harti Brandt <brandt@fokus.gmd.de> MFC after: 5 days
This commit is contained in:
parent
92277380c8
commit
0fb56449d6
@ -81,7 +81,7 @@ NgSendMsg(int cs, const char *path,
|
||||
/* Deliver message */
|
||||
if (NgDeliverMsg(cs, path, &msg, args, arglen) < 0)
|
||||
return (-1);
|
||||
return (gMsgId);
|
||||
return (msg.header.token);
|
||||
}
|
||||
|
||||
/*
|
||||
@ -146,7 +146,7 @@ NgSendAsciiMsg(int cs, const char *path, const char *fmt, ...)
|
||||
if (NgDeliverMsg(cs,
|
||||
path, binary, binary->data, binary->header.arglen) < 0)
|
||||
return (-1);
|
||||
return (gMsgId);
|
||||
return (binary->header.token);
|
||||
}
|
||||
|
||||
/*
|
||||
|
Loading…
Reference in New Issue
Block a user