On Thursday, August 21 2014, Emilio Lopes wrote:
>> I could not reproduce the problem here. Would you mind providing the
>> structure declaration, or at least a reproducer?
>
> Hello Sergio,
>
> thank you very much for your prompt answer!
>
> Here is the declaration of the structure:
Thanks, Emi
> I could not reproduce the problem here. Would you mind providing the
> structure declaration, or at least a reproducer?
Hello Sergio,
thank you very much for your prompt answer!
Here is the declaration of the structure:
typedef struct param_t {
const char* name;
type_t type;
s
On Thursday, August 21 2014, Emilio Lopes wrote:
> I'm having trouble trying to display structure members with names like
> C keywords. GDB refuses to display the member called `complex' in
> this case.
Hello Emilio,
> Here is the structure:
>
> (gdb) p g_global_paramv[37].info
> $27 =
On Wednesday, August 20 2014, Hádrian R wrote:
> Hi, I'm Kaiwaiata, since more than 2h searching and finding various
> possible vulnerabilities in source code of GDB..
> I will tell you one vulnerability now, if they treat me well I will tell
> the other..
Hello Kaiwaiata,
Thanks for the messa
I'm having trouble trying to display structure members with names like
C keywords. GDB refuses to display the member called `complex' in
this case.
Here is the structure:
(gdb) p g_global_paramv[37].info
$27 = {
complex = {
paramc = 20,
paramv = 0xd14f4 <_sys_opt>
Hi, I'm Kaiwaiata, since more than 2h searching and finding various
possible vulnerabilities in source code of GDB..
I will tell you one vulnerability now, if they treat me well I will tell
the other..
foolish or important things?
unsafe use of *strcpy()* in *int net_open (.. ..){**:*
*gdb-7.8