Re: Double free() in libc or gdb ?
On Tue, Mar 13, 2012 at 01:40:12PM +0100, Alexandre Martins wrote: > Two other thing > - The process consume memory, but there is no allocation in my code. Maybe a > leak in the libc ? No, this is a leak in rtld. I fixed it in r233546. > - My kernel have crashed after some minute of leak (i have removed printf > for > better perf on the loop). Maybe unrelated, but ... > pgpurZXqIh4Xf.pgp Description: PGP signature
Re: Double free() in libc or gdb ?
On Tuesday 13 March 2012 20:44:43 you wrote: > On 2012-03-13 11:08, Alexandre Martins wrote: > > On Monday 12 March 2012 18:55:55 Konstantin Belousov wrote: > >> On Mon, Mar 12, 2012 at 05:50:33PM +0100, Alexandre Martins wrote: > ... > > >>> I have the libc compilled with "MALLOC_DEBUG" flag to detect double > >>> free. When i run this piece of code (attached file) thought GDB, i > >>> have this assertion : > >>> > >>> Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function > >>> arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line > >>> 2543. > > I have committed a fix for this assertion (actually a double free) in > r232934. Can you please update to that revision, rebuild your gdb, and > try again? Dear, The problem have disapear with an update to gdb 7.3. Thank you for your help ! Regards -- Alexandre Martins NETASQ -- We secure IT
Re: Double free() in libc or gdb ?
On 2012-03-13 11:08, Alexandre Martins wrote: > On Monday 12 March 2012 18:55:55 Konstantin Belousov wrote: >> On Mon, Mar 12, 2012 at 05:50:33PM +0100, Alexandre Martins wrote: ... >>> I have the libc compilled with "MALLOC_DEBUG" flag to detect double free. >>> When i run this piece of code (attached file) thought GDB, i have this >>> assertion : >>> >>> Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function >>> arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line 2543. I have committed a fix for this assertion (actually a double free) in r232934. Can you please update to that revision, rebuild your gdb, and try again? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Double free() in libc or gdb ?
Dear, On Tuesday 13 March 2012 15:18:31 jb wrote: > Alexandre Martins netasq.com> writes: > > ... > > first.c: > > ... > > second.c > > ... > > main.c > > ... > > > > while(42) > > How do you exit that loop ? It's just a sample. There is no exit here, you have to kill the process. > > > ... > > Compilation and execution : > > > > gcc -shared -O0 -g second.c -o second.so > > gcc -shared -O0 -g first.c -o libfirst.so > > gcc -O0 -g toto.c -lfirst -L. -o test > > export LD_LIBRARY_PATH=$PWD > > gdb ./test > > ... > > What is your toto.c (source code) ? > What about your main.c in compilation ? Yes, you're right. "toto.c" is the "main.c" file. > > jb > > > > > > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" To Konstantin Belousov : The GDB v7.3 solved the assert. but is still memleak. Regards -- Alexandre Martins NETASQ -- We secure IT
Re: Double free() in libc or gdb ?
Alexandre Martins netasq.com> writes: > ... > first.c: > ... > second.c > ... > main.c > ... > while(42) How do you exit that loop ? > ... > Compilation and execution : > > gcc -shared -O0 -g second.c -o second.so > gcc -shared -O0 -g first.c -o libfirst.so > gcc -O0 -g toto.c -lfirst -L. -o test > export LD_LIBRARY_PATH=$PWD > gdb ./test > ... What is your toto.c (source code) ? What about your main.c in compilation ? jb ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Double free() in libc or gdb ?
On Tuesday 13 March 2012 13:17:52 Konstantin Belousov wrote:
> On Tue, Mar 13, 2012 at 11:08:40AM +0100, Alexandre Martins wrote:
> > On Monday 12 March 2012 18:55:55 Konstantin Belousov wrote:
> > > On Mon, Mar 12, 2012 at 05:50:33PM +0100, Alexandre Martins wrote:
> > > > Dear all,
> > > >
> > > > I'm currently having some trouble with the dynamic loader.
> > > >
> > > > I have the libc compilled with "MALLOC_DEBUG" flag to detect double
> > > > free. When i run this piece of code (attached file) thought GDB, i
> > > > have this assertion :
> > > >
> > > > Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0),
> > > > function arena_run_reg_dalloc, file
> > > > /usr/src/lib/libc/stdlib/malloc.c, line 2543.
> > > >
> > > > But when i run the same binary without GDB, no assert.
> > > >
> > > > I'm very confused. Can you help me to debug that ?
> > >
> > > There is no attachment. Put the source somewhere on web.
> >
> > Sorry, I'll past code here :
> >
> > first.c:
> >
> > #include
> >
> > void print_name(void)
> > {
> >
> > printf("I'm " __FILE__ " at line %d\n", __LINE__);
> >
> > }
> >
> >
> > second.c
> >
> > #include
> >
> > void second_name(void)
> > {
> >
> > printf("I'm " __FILE__ " at line %d\n", __LINE__);
> >
> > }
> >
> > void print_name(void)
> > {
> >
> > printf("I'm " __FILE__ " at line %d\n", __LINE__);
> >
> > }
> >
> >
> > main.c
> >
> > #include
> > #include
> >
> > extern void print_name(void);
> >
> > int main(int argc, char *argv[])
> > {
> >
> > void (*second_name)(void);
> > void *handle;
> > int count = 0;
> >
> > while(42)
> > {
> >
> > print_name();
> > handle = dlopen("second.so", RTLD_NOW);
> > print_name();
> > if (handle != NULL)
> > {
> >
> > second_name = dlsym(handle, "second_name");
> > if (second_name != NULL)
> > {
> >
> > printf("second : ");
> > second_name();
> >
> > }
> > dlclose(handle);
> >
> > }
> > else
> >
> > fprintf(stderr, "Error : %s\n", dlerror());
> >
> > }
> >
> > }
> >
> >
> > Compilation and execution :
> >
> > gcc -shared -O0 -g second.c -o second.so
> > gcc -shared -O0 -g first.c -o libfirst.so
> > gcc -O0 -g toto.c -lfirst -L. -o test
> > export LD_LIBRARY_PATH=$PWD
> > gdb ./test
>
> First, the libc malloc is not used inside rtld, so assertion which you
> see points to somebody else. This somebody could be the stdio in your
> example, or it could be gdb.
>
> On the HEAD r232862, I indeed get the assertion, that obviously comes
> from gdb. So this is a bug in gdb. Probably, try devel/gdb from ports,
> I hardly can help you with gdb bug.
Dear,
Thank for your response.
Two other thing
- The process consume memory, but there is no allocation in my code. Maybe a
leak in the libc ?
- My kernel have crashed after some minute of leak (i have removed printf for
better perf on the loop). Maybe unrelated, but ...
Regards,
--
Alexandre Martins
NETASQ -- We secure IT
Re: Double free() in libc or gdb ?
On Tue, Mar 13, 2012 at 11:08:40AM +0100, Alexandre Martins wrote:
> On Monday 12 March 2012 18:55:55 Konstantin Belousov wrote:
> > On Mon, Mar 12, 2012 at 05:50:33PM +0100, Alexandre Martins wrote:
> > > Dear all,
> > >
> > > I'm currently having some trouble with the dynamic loader.
> > >
> > > I have the libc compilled with "MALLOC_DEBUG" flag to detect double free.
> > > When i run this piece of code (attached file) thought GDB, i have this
> > > assertion :
> > >
> > > Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function
> > > arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line 2543.
> > >
> > > But when i run the same binary without GDB, no assert.
> > >
> > > I'm very confused. Can you help me to debug that ?
> >
> > There is no attachment. Put the source somewhere on web.
>
> Sorry, I'll past code here :
>
> first.c:
>
> #include
>
> void print_name(void)
> {
> printf("I'm " __FILE__ " at line %d\n", __LINE__);
> }
>
>
> second.c
>
> #include
>
> void second_name(void)
> {
> printf("I'm " __FILE__ " at line %d\n", __LINE__);
> }
>
> void print_name(void)
> {
> printf("I'm " __FILE__ " at line %d\n", __LINE__);
> }
>
>
> main.c
>
> #include
> #include
>
> extern void print_name(void);
>
> int main(int argc, char *argv[])
> {
> void (*second_name)(void);
> void *handle;
> int count = 0;
>
> while(42)
> {
> print_name();
> handle = dlopen("second.so", RTLD_NOW);
> print_name();
> if (handle != NULL)
> {
> second_name = dlsym(handle, "second_name");
> if (second_name != NULL)
> {
> printf("second : ");
> second_name();
> }
> dlclose(handle);
> }
> else
> fprintf(stderr, "Error : %s\n", dlerror());
> }
> }
>
>
> Compilation and execution :
>
> gcc -shared -O0 -g second.c -o second.so
> gcc -shared -O0 -g first.c -o libfirst.so
> gcc -O0 -g toto.c -lfirst -L. -o test
> export LD_LIBRARY_PATH=$PWD
> gdb ./test
>
First, the libc malloc is not used inside rtld, so assertion which you
see points to somebody else. This somebody could be the stdio in your
example, or it could be gdb.
On the HEAD r232862, I indeed get the assertion, that obviously comes
from gdb. So this is a bug in gdb. Probably, try devel/gdb from ports,
I hardly can help you with gdb bug.
pgpImfzbk6lrz.pgp
Description: PGP signature
Re: Double free() in libc or gdb ?
On Monday 12 March 2012 18:55:55 Konstantin Belousov wrote:
> On Mon, Mar 12, 2012 at 05:50:33PM +0100, Alexandre Martins wrote:
> > Dear all,
> >
> > I'm currently having some trouble with the dynamic loader.
> >
> > I have the libc compilled with "MALLOC_DEBUG" flag to detect double free.
> > When i run this piece of code (attached file) thought GDB, i have this
> > assertion :
> >
> > Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function
> > arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line 2543.
> >
> > But when i run the same binary without GDB, no assert.
> >
> > I'm very confused. Can you help me to debug that ?
>
> There is no attachment. Put the source somewhere on web.
Sorry, I'll past code here :
first.c:
#include
void print_name(void)
{
printf("I'm " __FILE__ " at line %d\n", __LINE__);
}
second.c
#include
void second_name(void)
{
printf("I'm " __FILE__ " at line %d\n", __LINE__);
}
void print_name(void)
{
printf("I'm " __FILE__ " at line %d\n", __LINE__);
}
main.c
#include
#include
extern void print_name(void);
int main(int argc, char *argv[])
{
void (*second_name)(void);
void *handle;
int count = 0;
while(42)
{
print_name();
handle = dlopen("second.so", RTLD_NOW);
print_name();
if (handle != NULL)
{
second_name = dlsym(handle, "second_name");
if (second_name != NULL)
{
printf("second : ");
second_name();
}
dlclose(handle);
}
else
fprintf(stderr, "Error : %s\n", dlerror());
}
}
Compilation and execution :
gcc -shared -O0 -g second.c -o second.so
gcc -shared -O0 -g first.c -o libfirst.so
gcc -O0 -g toto.c -lfirst -L. -o test
export LD_LIBRARY_PATH=$PWD
gdb ./test
Thank you for your help
--
Alexandre Martins
NETASQ -- We secure IT
Re: Double free() in libc or gdb ?
On Mon, Mar 12, 2012 at 05:50:33PM +0100, Alexandre Martins wrote: > Dear all, > > I'm currently having some trouble with the dynamic loader. > > I have the libc compilled with "MALLOC_DEBUG" flag to detect double free. > When i run this piece of code (attached file) thought GDB, i have this > assertion : > > Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function > arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line 2543. > > But when i run the same binary without GDB, no assert. > > I'm very confused. Can you help me to debug that ? There is no attachment. Put the source somewhere on web. pgprMtcFQlRgB.pgp Description: PGP signature
