|
What does that have to do with "get_string memory leak"?
|
|
|
|
|
Just the fact that’s not wise to assume the error is someone else’s code. Better to try to understand what’s going on and discover what atexit function does.
Next step would be to eventually figure out that the “constructor” code is contrived and the call to atexit could be done on first allocation.
Edit: not sure to what message was your reply. Stuck to a cell phone today and CP is not the greatest on mobile. Apologies if I’m confusing you.
Mircea
|
|
|
|
|
First the question is about a method that may leak memory, then a sudden jump-cut a post about bubble sort pseudocode, then another jump-cut to your philosophy.
To say I'm confused as to what's going on with this thread is an understatement.
|
|
|
|
|
Apologies again! I thought your message was directed at my answer. Anyway I'll try to cut the philosophy c**p in the future; it's waste of time.
Mircea
|
|
|
|
|
mike7411 wrote: I think it has a memory leak.
Despite the other posts - yes this would be a classic example of a memory leak.
The teardown() method, as used, is pointless. When the application exits (on every modern OS including small ones) the memory that the application uses is returned to the OS. So the fact that teardown is called on the application exit via the atexit() method is absolutely pointless.
If you were to use the code in a regular application, especially but not limited to one that does not exit, then this would fail. Because of memory leaks. You could not call teardown() arbitrarily either because it would clear everything.
Now it is possible that the point of the code is not to teach you efficient memory usage. But one could certainly argue that the get_string() method should make it clear that this is not a good way to do things.
However the following is in comment for that method.
Stores string
on heap, but library's destructor frees memory on program's exit.
And that indicates that the creator of this code did not understand/know what I pointed out above.
The code also has a copyright date of 2023 so there is no claim that the code could have been written, for example 50 years ago, where one might (perhaps) have used an OS where the application would have needed to do that. Note however that even then I am not sure any OSes actually worked that way. Back then PC-DOS, CPM and early unix versions (there was no linux) returned memory to the OS.
You can take from this that you should not write code like this.
In general in C and C++ you should always control the scope of your memory allocations. So for example if your method allocates some memory then that same method should deallocate (all exit conditions for the method included.) There should almost never be a need to have a method return an allocation and if it does happen then the method should document (comment) that the caller is responsible for the allocation.
C++ makes this easier since you can wrap the allocation in a class. And control allocation/deallocation from that. That is something that I would suggest always doing. So in C++ you would never return an allocated pointer.
|
|
|
|
|
You've covered everything I was going to say, and then some. I was not sure what early versions of DOS might have done with allocated memory at program exit, but it's nice to know that even then, an most OS's would do the Right Thing™.
The code looks like it comes from the early 80's. That it should come from a prestigious university (it is that Harvard, right?), that should know better, is disheartening. Although, it might be a shining example of what not to do.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
Actually, you, like I do, should question the exisitential "being" of said OP, if this is any indication of a sentience which can't be gleened from his reputation due to the fact that there is no access to said: mike7411 - Professional Profile[^]
I know, I know. A kite joke. 
|
|
|
|
|
k5054 wrote: That it should come from a prestigious university (it is that Harvard, right?), that should know better
That of course doesn't mean anything.
Large organizations, all large organizations, tend towards the average. That is inevitable due to size.
Besides that there is no determination about an individuals competence in general or for specific things.
You can also google for variations of the code library and find variations. I found a variation that looked like it was C++. No memory leak in that (very brief look) because it was returning 'string'. So possible that someone familiar with C++ but not so much C converted it. And also possible it wasn't even the person teaching the class, just that the teacher found it and is using it.
|
|
|
|
|
Harvard esp. so 
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
First - my apology for taking so much space, I promise to delete ALL after I get this solved - unless it is of benefit to forum...
Here is the current status of "main menu with sub menus "
using "connect" with lambda - it works only on FIRST menu.
I believe the sender and subsequent trigger are WRONG.
I am enclosing the code which creates
the " main menus with their associated sub menus ".
The code works as expected / desired.
The issue is using "connect" as a trigger..sub menu selection...
{ for (index = 0; index < list.size(); ++index)
{
{ { subMenu[index] = m_ui->menuWindow_cpntrol;
subMenu[index] = subMenu[index]
->addMenu(list[index] + " # " + QString::number(index));
mainAction[index] = subMenu[index]->menuAction();
subSize = list_array[index].size();
for (index_sub = 0; index_sub < subSize; ++index_sub)
{ { { subAction[index_sub]= subMenu[index]->addAction(list_array[index][ index_sub] + " #" + QString::number( index_sub));
subAction[index_sub]->setCheckable(true);
} } } }
QAction* tempAction = new QAction(); tempAction->setCheckable(true);
{ }
{ {
} }
{
{}
} } }
{
}
}
Here is my current, working with FIRST menu code.
I do apology for "debug" junk code , it is a little hard to follow the real code.
{
#ifdef LAMBDA
text = "START TASK DEBUG lambda ... ";
text += Q_FUNC_INFO;
text += QString::number(__LINE__);
qDebug() << text;
#endif
int submenu_index = -1;
int mainmenu_index= -1;
QString mainMenu;
QObject obj;
qDebug() << " index_sub " << index_sub ; obj.connect(subMenu[index_sub],&QMenu::triggered,subMenu[index_sub ],[](QAction* action)
{
QString path=action->text();
#ifdef LAMBDA
qDebug() << "TEST need index ?? " << path;
qDebug()<<"path (sub menu trigger ) "<< path ;
#endif
QWidget* parent=action->parentWidget();
path = QString("(%1)").arg(parent->actions().indexOf(action));
#ifdef LAMBDA
qDebug()<<"path (sub menu ) with index TOK "<< path ;
#endif
while(parent)
{
QMenu* menu=qobject_cast<QMenu*>(parent);
QString title=menu->title();
#ifdef LAMBDA
qDebug()<<"title (main menu ) "<< title ;
#endif
path+="->"+title;
qDebug()<<"path (title) "<< path ;
parent=parent->parentWidget();
#ifdef LAMBDA
qDebug()<<"TRACE while first entry crasher ... "<< __LINE__ ;
#endif
if(parent)
{
#ifdef LAMBDA
qDebug()<<"TRACE parent widget (??) valid continue ... "<< __LINE__ ;
#endif
QMenu* menu=qobject_cast<QMenu*>(parent);
#ifdef LAMBDA
qDebug()<<"TRACE parent widget main menu (??)continue "<< __LINE__ ;
#endif
int index=0;
const QList<QAction*> actions=menu->actions();
#ifdef LAMBDA
qDebug()<<"TRACE parent widget main menu list (actions) continue "<< __LINE__ ;
#endif
for(const QAction *act : actions)
{
#ifdef LAMBDA
qDebug()<<"TRACE for(const QAction *act : actions) "<< __LINE__ ;
#endif
#ifdef LAMBDA
qDebug()<<"TRACE title (??) " << title << __LINE__ ;
#endif
#ifdef LAMBDA
qDebug()<<"TRACE act->text()==title "<< act->text() << __LINE__ ;
#endif
if(act->text()==title)
{
#ifdef LAMBDA
qDebug()<<"TRACE main menu found act->text()==title "<< act->text() << __LINE__ ;
#endif
path = QString("(%1)").arg(index);
#ifdef LAMBDA
#endif
#ifdef LAMBDA
qDebug()<<"HERE path (main menu -> sub menu) "<< path ;
#endif
goto TEMP_LABEL;
}
#ifdef LAMBDA
qDebug()<<"TRACE "<< __LINE__ ;
#endif
index++;
}
}
} TEMP_LABEL: qDebug()<<" FINAL (??) "<< path;
} );
QString::number(__LINE__);
#ifdef LAMBDA
text = "END TASK DEBUG lambda... ";
text += Q_FUNC_INFO;
text += QString::number(__LINE__);
qDebug() << text;
#endif
return 0;
}
'
Here is more junk - actual debug output when first "main menu" and its "first sub menu " is selected - by triggering on first sub menu.
19:53:10: Starting /mnt/A_BT_DEC10/BT__PROGRAMS/A_JAN11/A_BT_LIBRARY/mdi/mdi...
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
"START TASK DEBUG lambda ... int MainWindow_Bluetooth::setupLambda()89"
index_sub 0
"END TASK DEBUG lambda... int MainWindow_Bluetooth::setupLambda()213"
TEST need index ?? "SubWindow LOCAL terminal all options #0"
path (sub menu trigger ) "SubWindow LOCAL terminal all options #0"
path (sub menu ) with index TOK "(0)"
title (main menu ) "terminal # 0"
path (title) "(0)->terminal # 0"
TRACE while first entry crasher ... 138
TRACE parent widget (??) valid continue ... 143
TRACE parent widget main menu (??)continue 149
TRACE parent widget main menu list (actions) continue 154
TRACE for(const QAction *act : actions) 163
TRACE title (??) "terminal # 0" 166
TRACE act->text()==title "Tile subwindows " 169
TRACE 194
TRACE for(const QAction *act : actions) 163
TRACE title (??) "terminal # 0" 166
TRACE act->text()==title "Cascade subwindows " 169
TRACE 194
TRACE for(const QAction *act : actions) 163
TRACE title (??) "terminal # 0" 166
TRACE act->text()==title "Maximize current subwindow " 169
TRACE 194
TRACE for(const QAction *act : actions) 163
TRACE title (??) "terminal # 0" 166
TRACE act->text()==title "" 169
TRACE 194
TRACE for(const QAction *act : actions) 163
TRACE title (??) "terminal # 0" 166
TRACE act->text()==title "" 169
TRACE 194
TRACE for(const QAction *act : actions) 163
TRACE title (??) "terminal # 0" 166
TRACE act->text()==title "terminal # 0" 169
TRACE main menu found act->text()==title "terminal # 0" 175
HERE path (main menu -> sub menu) "(5)"
FINAL (??) "(5)"
19:53:27: /mnt/A_BT_DEC10/BT__PROGRAMS/A_JAN11/A_BT_LIBRARY/mdi/mdi exited with code 0
Here is the failure when ANY main menu , with exception of first one , is used.
That points to probable cause - wrong sender....
19:31:40: Starting /mnt/A_BT_DEC10/BT__PROGRAMS/A_JAN11/A_BT_LIBRARY/mdi/mdi...
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
"START TASK DEBUG lambda ... int MainWindow_Bluetooth::setupLambda()89"
index_sub 0
"END TASK DEBUG lambda... int MainWindow_Bluetooth::setupLambda()213"
19:31:54: /mnt/A_BT_DEC10/BT__PROGRAMS/A_JAN11/A_BT_LIBRARY/mdi/mdi exited with code 0
|
|
|
|
|
Best guess? Wrong forum. AFAICT this is a QT issue. QT ≠ C++. While QT does use C++ as a base, it's a framework on top of C++. You are more likely to get an answer either from a QT specific forum, or from the site you got your examples from.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
So you do not think this is my fault - wrong usage of C++?
"connect " is Qt specific , but lambda is C++ or am I wrong?
I did post same on QT forum and I fully expect somebody to say _ this is C++ code problem "...
But if I continue this discussion here ... I will end up banned......
.,..in that case..
Thanks and have a swell day...
|
|
|
|
|
I'm basing this on the runtime error, which you believe is something to do with "wrong sender". That seems to me to be a QT issue, not a C++ issue. AFAIK, there's no such thing as a "sender" in the C++ standard. Which points to QT, not C++
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
OK, it is Qt issue..
I'll give few days for somebody else to respond , then I
will take it down.
Is that OK?
|
|
|
|
|
I'd just leave it, unless more senior members disagree. Otherwise, there's a discussion that someone else might stumble on and wonder what was going on. Who knows, maybe someone will stumble on this at some time in the future and be able to explain what the issue is.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
Here is my analysis in a nutshell.
The "issue" is with Qt "connect" function / process...
I have the "connect" working as expected , but ...
I am passing parameters / indexes - main menu and submenu...
...that is what I thought I was doing , but ...
the "parameters " values are NOT dynamic AKA
used when "connect" is activated - click on sub menu.
In my test - the main menu should be 0
and the submenu anything from 0 to 7
The code I have found uses lambda
and it analyze the "connect" AND
RETRIEVES the dynamic values of both indexes.
I need the indexes to do what the menu / submenu
is about - process something...
I have modified the code because i
CANNOT debug / step thru the lambda code !
So - the lambda code does work BUT ...
it only works/ retrieves main menu index of 0
That is the real error and I am seeking assistance
to find out why
it only works on FIRST menu.
My uneducated guess is -
the obvious place
to look is where
the code step thru "main menu list"...
if(parent)
{
QMenu* menu=qobject_cast<QMenu*>(parent);
int index=0;
const QList<QAction*> actions=menu->actions();
for(const QAction *act : actions)
{
if(act
->text()==title)
{
path+=QString("(%1)").arg(index);
break;
}
index++;
}
}
|
|
|
|
|
Salvatore Terress wrote: I have modified the code because i
CANNOT debug / step thru the lambda code !
That does seem to be an issue with lambdas - at least gdb doesn't seem to be able to step into lambdas. I haven't tried it myself, so I can only go by what I've seen elsewhere on the subject.
But.
Why don't you just extract the function definition from the lambda and define it as a normal function. I think that should work
foo( a, b, c, [](int x, int y) { return val; } );
becomes
int lambda_f( int x, int y)
{
return val;
}
foo(a, b, c lambda_f);
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
Yes, I am now using plain function to analyze results of "connect".
My code is still pretty messy , hard to read , since I added debug...
But I can step thru it , so the debug is "leftover from lambda"...
I got my code doing what I need...
In retrospect - the problem was what I suspected from the start
understanding "connect" and PLACING it into correct place.
PS
As far as getting help from forums - it was ABOUT 80% of "RTFM" and other
"fill the blanks" to make "small talk"...
|
|
|
|
|
Salvatore Terress wrote: then I
will take it down.
Is that OK?
No, because that leaves orphaned messages which make little sense to others reading it.
Incidentally, I did look at this code earlier and tried to make it readable, by removing all those extra braces in the first sample, but it still made little sense. As to the second sample, why are you trying to use a lambda expression for all that code? Use a proper function/member subroutine so you can see better what is (supposed to be) happening. And, as k5054 says, this is most likely a Qt issue rather than simple C++.
|
|
|
|
|
Richard MacCutchan wrote: why are you trying to use a lambda expression for all that code?
I agree with that strongly.
If the developer can't figure out the lambda code then they shouldn't be using it in the first place. That isn't being denigrating since to me they are almost always confusing so I never voluntarily use them. They do nothing but make the code obtuse and the more complicated it is the more that becomes true.
It also has the following impacts.
- Maintenance programmers must figure it out.
- I have seen more than one senior developer use it incorrectly making the code less efficient.
Seems almost like there could be a coding guideline in that. If methods must be, for example, less than 100 lines of code, then seems that lambda expressions should also be limited perhaps to something like 10 clauses (or less.)
|
|
|
|
|
Please read my previous reply.
It was not my choice to use lambda - I took the code from another forum contributor...
Using lambda was not that difficult - the code flow was pretty logical.
The issue was - for whatever reason I could not "step thru" the lambda code...
|
|
|
|
|
I fully understand that. What I'm saying is that there is no reason that you to have to use a lambda. You can extract the function body and use a normal function pointer instead. And a normal function can be debugged by putting a break point a the function entry point.
I'm not sure what your stumbling point is here. Consider:
struct S {
int i;
double d;
};
bool cmp_double(const S& s1, const S&s2) {
return s1.d < s2.d;
}
int main()
{
std::vector<S> vs;
std::sort( vs.begin(), vs.end(), cmp_double);
std::sort( vs.begin(), vs.end(), [](const S& x, const S&y) { return x.d < y.d } );
}
The point is, the two sorts do exactly the same thing. So there's no reason you can't extract the lambda and use the named function as a parameter. If you're having trouble understanding this, you need to go back to your study material and review lambdas. I can recommend Justin Turners C++ weekly you-tube blog [https://www.youtube.com/playlist?list=PLs3KjaCtOwSZ2tbuV1hx8Xz-rFZTan2J1](https://www.youtube.com/playlist?list=PLs3KjaCtOwSZ2tbuV1hx8Xz-rFZTan2J1) Just follow the link and then search for lambda, and watch the videos. It might be worth doing even if you do understand lambdas. It's not like another perspective can't help with the understanding.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
Salvatore Terress wrote: It was not my choice to use lambda - I took the code from another forum contributor
Pretty sure that is a choice. As suggested in the other post you can rewrite it.
Not sure I have ever used a code sample where I did not modify it.
|
|
|
|
|
|
It counts the initial characters in the string until the pointer is aligned on a longword boundary. It then uses some clever bit manipulations to count the rest of the characters four at a time. If you run that code in the debugger you will be able to see exactly what happens.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
